drac
I'm sad about this, I loved programming Perl a decade ago but the last side project I wrote in Perl was all the way back in 2010.
The comparison with the M-16 in particular is pretty brutal.
Great site, I can see myself hitting the right arrow key for hours on end :)
In many cases, will we even know if it was mutual or just an understandable need for a change of scene? Contrast the departures of Bret Anderson from Facebook, Naveen Selvadurai of Foursquare and Marco Arment from Tumblr [and these are just CTO/co-founder examples]
Still no email (an hour or so later) :) - tbf, there's about 3000 links
The tree lined boulevards in my city routinely disrupt traffic after monsoon rains - most are close to 40 years old, and every so often will shed a branch or three onto the road.
Minor typo: Let it be investors, founders, owners or just jourself should be "yourself".
I know Perl better than most other languages in my toolbox, and it's my default prototyping and one-off utility language. I don't find a lot of niches (for my typical uses, of course) that are served better by Ruby, so it's been really difficult to switch away from Perl.
Yet the problem now is if you spend all that time communicating, you still can't know for sure if everyone was listening or tuning you out half the time. More so if other people around you undercommunicate instead of overcommunicate.
Perhaps it is not the norm but I've seen this response to a few leaders who spend a lot of time communicating. Wonder if it is worth it, always
Which basically means, I only experience honked annoyance about 2-3 times a week on average.
The blatant disregard for posted speed limits in my corner of MA? Even with police cars parked on the side of the road? Yeah, that I just don't get.
No upgrade from SP2? Well, IE 6 and only IE 6 it is then.
A related issue: IE 8 offers the ability to run in IE 7 compatibility mode, with the inclusion of a header in the source web page. Despite dire warnings to the contrary, some website developers for UK government insist on setting the header and declaring that IE 8 compatibility has been achieved. I can't wait to see how that will end, to be honest.
The tiering system goes something like this: Software Engineer -> Lead -> Architect
Without advancing through the ranks, it is well nigh impossible to get reasonable increases in pay; so people (even those who may wish to write more code) strive to climb up the ladder.
Not saying it makes perfect sense to everyone, but there is some logic to making sure people climb up the ladder quickly (if they are capable) in large corporations.
The other thing I've noticed with a large number of dial-in participants is that there can be a lot of silent attendees and very few people talking. YMMV
In your example - it was a single task. Working with the assumption that domain expertise can be acquired on the job, the costs of doing subsequent jobs will be lower for the outsourced engineer.
The more times the same task needs to be performed by the engineer, the cheaper outsourcing becomes. Your example just accounted for the startup cost, which can be assumed to be a one-off*
*Is it that way in practice? at least in some projects, it is.