+1
On 20 June 2012 12:44, Andrew Snow wrote:
>
> In my RoRo travels, I've been initiator of, the recipient of, and privy
> to, disparaging remarks about "the previous bunch of n00bs" who were the
> last developers to touch a project.
>
> This happens on projects big and small, by both profession
On Wed, Jun 20, 2012 at 12:44 PM, Andrew Snow wrote:
> But because you don't know the circumstances:
> * the budget
> * the deadlines
> * politics
> * promises and obligations
> * vague scope
> * creeping scope, etc
> I think it unwise to pass judgment on the "previous guy", whether to the
This is why we have the term "past me" to refer to that "other developer" who
looks and talks exactly like you but cannot possibly be you because the code is
so smell.
It's respectful to only invoke the term "past me", "past you" is considered
impolite.
Mother Rufus
On Wednesday, 20 June
I've definitely been there - brought in on a "rescue project" at a large
Australian business, called in to take over after a bunch of "cowboy
coders" had failed to meet a project milestone. The key proof of their
being cowboys was that they'd used Star Trek characters as the names for a
bunch of t
On 20/06/12 12:52, Daniel Draper wrote:
Andrew, I totally agree. My comments were not meant to be disparaging to
any individual. They were meant as a lighthearted poke - and directed at
a group more so than any one individual.
Cool -- this wasn't specifically at you, I wanted to address the top
Andrew, I totally agree. My comments were not meant to be disparaging to
any individual. They were meant as a lighthearted poke - and directed at a
group more so than any one individual.
I sincerely apologise, once again for an oversight in judgement.
On 20 June 2012 12:14, Andrew Snow wrote:
>
Well said. ❤
--
You received this message because you are subscribed to the Google Groups "Ruby
or Rails Oceania" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/rails-oceania/-/BmqWLGZvJKIJ.
To post to this group, send email to rails-oceania@googlegroups.com.
In my RoRo travels, I've been initiator of, the recipient of, and privy
to, disparaging remarks about "the previous bunch of n00bs" who were the
last developers to touch a project.
This happens on projects big and small, by both professionals of many
years experience, all the way down to non
agreed. i think it should have been deleted in the first place though until
a better version was produced.
On Wednesday, 20 June 2012 12:28:58 UTC+10, Mark Wotton wrote:
>
> In general, there's a blanket rule not to respond to job ads on-list,
> and this is probably a good example of why we hav
Immature. Trolling. And I probably should stop it as well.
On Wednesday, 20 June 2012 12:20:36 UTC+10, Daniel Draper wrote:
>
> Maybe instead of wasting time complaining about how I have "wronged" (a
> nameless developer) you should go and write some tests for your code!
>
> On 20 June 2012 11:4
In general, there's a blanket rule not to respond to job ads on-list,
and this is probably a good example of why we have the rule.
Metacommentary -> twitter/irc.
cheers
Mark
On Wed, Jun 20, 2012 at 12:20 PM, Daniel Draper wrote:
> Maybe instead of wasting time complaining about how I have "wrong
Maybe instead of wasting time complaining about how I have "wronged" (a
nameless developer) you should go and write some tests for your code!
On 20 June 2012 11:47, Marc wrote:
>
> IMHO someone who hasn't written tests has not done their job properly
> (albeit even if they were forced by powe
IMHO someone who hasn't written tests has not done their job properly
(albeit even if they were forced by powers that be)
that comment seems rather close-minded towards the possibilities that may
have occurred for the developer not to write tests. Tests are highly
important but there are al
Guys,
The client approached Codefire a while back for help on their project. We
were taking it over from another developer and I'm not meaning to be
disrespectful (or to "publicly humiliate" them) but the project was simply
not up to scratch. We have done quite a bit of refactoring and it is bette
No it wasn't our project initially.
On 20 June 2012 09:26, Keith Pitt wrote:
> "powers that be?" - you're the CEO. Doesn't that make YOU the power that
> be?
>
> --
> @keithpitt
>
> On Tuesday, 19 June 2012 at 5:04 PM, Daniel Draper wrote:
>
> I didn't name anybody and IMHO someone who hasn't wr
"powers that be?" - you're the CEO. Doesn't that make YOU the power that be?
--
@keithpitt
On Tuesday, 19 June 2012 at 5:04 PM, Daniel Draper wrote:
> I didn't name anybody and IMHO someone who hasn't written tests has not done
> their job properly (albeit even if they were forced by powers
(Apologies in advance for the cross-post if you're also on the Railscamp group)
As some of you are probably aware by now, although the dust has barely settled
from RC11, RailsCamp 12 planning is underway and the location is Tasmania.
Details:
When: Starts Friday, November 16th, runs until Monda
Sounds awesome,
Is there anything similar to this around Melbourne?
Dan
On Tuesday, June 19, 2012 1:39:04 PM UTC+10, Tim McEwan wrote:
>
> Hey Folks,
>
> I'm taking over from the venerable Mr Price this month to bring you a Hack
> Night at the Institute for Sustainable Futures (University of Te
Wow. OK, was just supposed to be a bit of light fun but I'll take your
comments on board and update the listing.
I didn't name anybody and IMHO someone who hasn't written tests has not
done their job properly (albeit even if they were forced by powers that
be). He also wasn't working for us. Apolo
19 matches
Mail list logo
