obie

8 ms·

1.
by obie 14y ago
"Nothing is more heartbreaking than realizing that a worker who is trying his hardest can’t cut it." So true. I've had to fire a few people that met that criteria and it's really difficult to do. In a startup situation, it might be advantag
2.
Geeks on a Plane Search for Startups(businessweek.com)
1 points by obie 14y ago|0 comments
3.
by obie 17y ago
Looks like it might have a sad ending -- the boy might have fallen out while the balloon was adrift.
4.
by obie 17y ago
The link to the source code (omitted in the article) is http://github.com/engineyard/rails_dev_directory
5.
by obie 17y ago
LOL, you just described the way that Rails first makes it into a lot of large organizations. Luckily, if you follow Rails conventions you should be pretty close to "production worthy" at step 6. As for step 10, it's the rare system that doe
6.
by obie 17y ago
Hook me up obie@hashrocket.com (thanks)
7.
by obie 17y ago
"Diving debt into reckless/prudent and deliberate/inadvertent implies a quadrant, and I've only discussed three cells. So is there such a thing as prudent-inadvertent debt? Although such a thing sounds odd, I believe that it is - and it's n
8.
Martin Fowler describes four kinds of "technical debt"(martinfowler.com)
38 points by obie 17y ago|16 comments
9.
Pair Programming Is For Everyone: A Rebuttal(blog.brianguthrie.com)
4 points by obie 17y ago|0 comments
10.
by obie 17y ago
Bravo! The burnout objection is laughable. Our consultants are required to bill 35 hours per week, which translates to an average of 7 hours of coding or less every day (there is billable work like meetings that is not writing production co
11.
by obie 17y ago
It's hard to do that on a client's dime, at least for me. (I know other consultancies do it all the time and it disgusts me.)
12.
by obie 17y ago
Absolutely. It took me four years of misstarts and agony (2000-2004) to really understand and get good at pair programming. During that time I mostly kept the faith about it since I was a zealous XP advocate, but had a large measure of doub
13.
by obie 17y ago
Thanks! :)
14.
by obie 17y ago
"Pair flow" is difficult to achieve, especially if you're new to pair programming. What you describe here is simply a dysfunctional pairing situation.
15.
by obie 17y ago
Happy to see this big step towards transparency. Don't like that it has waterfall concepts built in and excludes defense spending completely. But hey, it is progress and Fed CIO Vivek Kundra made progressive comments towards the importance
16.
Federal IT Dashboard Announced by CIO Kundra at Personal Democracy Forum '09(it.usaspending.gov)
2 points by obie 17y ago|1 comments
17.
by obie 18y ago
We've been using Pivotal Tracker at Hashrocket for over six months and it's an integral part of our success. It's an opinionated tool in the way that it codifies a successful Agile workflow between developers and their project stakeholders.