Might be worth a shot.
281 karma · joined October 22, 2011
Might be worth a shot.
To each his/her own I say.
The most problematic part of SCRUM (and the first thing to start killing productivity) are the interminable meetings it facilitates. The SCRUM master is constantly trying to gauge scope on this or that feature, and everyone feels like they need to bring up what they've been working on during the standup in order to feel like they're not appearing to be slacking off.
I've abandoned SCRUM in favor for a Kanban approach that puts the onus on the Product Owner to manage and estimate scope and deadlines, thereby leaving us developers alone to focus on our work.
I've written more about my approach here: https://medium.com/@glenelkins/agile-is-good-for-managers-bu...
That said, it probably depends on the type of person you are. If you're super outgoing and involved, freelancing full-time is probably similar to working at an agency in that regard, but if that's true it sort works against the point of your post.
And some of those whippersnappers are going to be rolling on the same technology stack 10 years from now."
I couldn't disagree with that sentiment more. I'm a developer who works full time at an agency and freelances on the side when I feel like it. I know a lot of developers my age (mid-late twenties) that have only really ever freelanced full time and never worked in a company 9-5 and I can say the one noticeable difference between us is the skill set.
being surrounded by better developers than I has forced me to learn new things in a way that striking out on my own would never do. Sure, necessity is the mother of invention, and if you're running your own business, you'll have to learn things to keep the lights on, but you miss out on all the mentorship and guidance working with a team of more experienced people gives you.
I've worked at around 4 agencies in my career thus far, and have never seen or heard of an agency that fits the description in your hyperbolic example. In fact, I tend to think it more closely resembles a one-man freelance dev shop.
Just my thoughts.
Sure, talking about servers, backends and all the nitty gritty is great fun and what I'd expect from HN absolutely, but the goal of writing is to communicate an idea to others, and how well you're service solves that problem will greatly pique my interest. The tech behind it is fun and important, but less so to solving the core problem of writing/communicating.
For example, I'd love to hear this expanded upon: "I built Silvrback because none of the existing blogging platforms satisfied me completely."
The white text on near-neon background is tough on my eyes.
Surprisingly, people do not take advantage. I think some less mature people may like to brag about how much they can code whilst drunk, but it's just like any other drug: If you can do X, Y, and Z incredibly well while under the influence, odds are you'd do even beter while sober.
If you can "get shit done" while drunk b/c you're no longer afraid of the awkward situations, odds are you'd do even better at handling them sober.
We've never had an awkward situation where someone checks in epically bad code due to being sloppy-drunk that I'm aware of, but that's b/c people are largely self-policing and they realize that what you an manage to do drunk, you can dominate sober.
I don't wish to sound like a prude. We do enjoy the refreshments, but usually after-hours, or at least when doing exploratory R&D, perhaps playing with a new design. To do your best work on the most important projects at a startup, you really to to bring your "A" game.
I commit to small one-off projects for friends, longer-term work with acquaintances, and whip up my own projects all the time. Sometimes the projects are freelance, and sometimes they are simply "free." All this serves to satiate the needling feeling in the back of my brain that I might just be missing out on something.
Here's the rest of my thoughts: http://blog.glenelkins.com/the-over-committers-dilemma/
Are there droves of people who could benefit from constantly changing css?
Perhaps I'm just missing something rather obvious. If so, please help me.
Patent issues alone, I find it very likely Jobs saw Google's foray into iOS as a direct assault on one of his flagship products.
I do not contend that the early morning is the most productive hours of the day. I usually take an hours or so to really warm up, get some coffee in me and start working well. Another common mistake I'll make is spending the hour+ time on checking emails, reading up on news, checking fantasy football & stock prices... all things that I'd normally do in my "personal time," yet do not have anything to do with my projects.
This idea definitely works, but requires discipline :)
Sometime you can have your cake and eat it too, although this doesn't solve a common problem when sourcing work . If the writer is uninterested or unfamiliar with the topic, the quality will invariably suffer.
* edited for grammar