The 501 Developer Manifesto
501manifesto.org
The 501 Developer Manifesto
1–10 of 120 posts
Re: The 501 Developer Manifesto
#2People who write technical blogs, go to user groups, or endlessly read programming books seem to be in the "not us" group, but I know of day job developers who do (some/all of) those things. Drawing lines in the sand doesn't seem useful when, I think, the issue behind this seems to be "don't look down on us day job developers." :-)
Re: The 501 Developer Manifesto
#3I was very pleasantly surprised. This is something I am definitely behind, even though for me it isn't just a job. I love programming, but for years my programming at home has languished because my programming at work is a soul-sucking endeavor that leads me to have a sinking feeling every time I look at the Komodo icon on my home PC.
I think the core problem here is not about an us versus them when it comes to the guys who go home to their wife and kids and the guys that go home to their git and vim. It's more about the fact that both groups probably spend too much time away from their homes, and right now the programming scene is incredibly fractured. Programmers are certainly not a homogenous group. Off the top of my head, I can think of about a dozen different flavors of programmer, all with their own innate perceptions about things both programming related and not.
What we really need is a coming together of the programmers-by-trade and the programmers-at-heart to declare war on all of the silly little stereotypes that have created a workplace unfairness in IT in the last fifteen to twenty years. You need a communion of individuals to create a semi-fraternal organization that looks like a union on the outside but inside is a diverse collective of brilliant minds.
It wont be easy, but many smart people (and a very few ridiculously articulate people) have been passively advocating for it in the last ten years or so, and I think that as the post-dotcom generation starts to move into their 30s we'll see a drastic change in the employee relationship within the next five to ten years.
Re: The 501 Developer Manifesto
#4Re: The 501 Developer Manifesto
#5Re: The 501 Developer Manifesto
#6I also make plenty of time for family and fun. Maybe it's all of those productivity books.
Re: The 501 Developer Manifesto
#7Just don't break the build at 4:59. That's all I ask.
Re: The 501 Developer Manifesto
#8Re: The 501 Developer Manifesto
#9There's a gulf between a stereotypical "day job" developer and someone for whom programming is a core part of their self image, but in real life there's more of a subtle gradient. People who write technical blogs, go to user groups, or endlessly read programming books seem to be in the "not us" group, but I know of day job developers who do (some/all of) those things. Drawing lines in the sand doesn't seem useful whe…
The bigger takeaway for me from the manifesto is the first half--that my job is my job. I enjoy my co-workers, but, truthfully, I enjoy my family and friends more. And that should be okay.