71–80 of 84 posts
[1]: http://libsound.io/
I'm the only developer in my ad agency of about 80 people. It's super cool to write all my own code, make all my own stack choices. To know that I wrote everything here is a really cool feeling. At the same time, I really miss talking shop with other devs. And given my extremely young age (only a few years out of school) sometimes it can be hard to be sure I'm making the most efficient choices. There's a lot of times…
I'm the only developer in my ad agency of about 80 people. It's super cool to write all my own code, make all my own stack choices. To know that I wrote everything here is a really cool feeling. At the same time, I really miss talking shop with other devs. And given my extremely young age (only a few years out of school) sometimes it can be hard to be sure I'm making the most efficient choices. There's a lot of times…
I did that for 4 years. Beware! Being the only tech at an "agency" will quickly atrophy your core engineering skills, if you're not careful. You will get _good_ at delivering working solutions quickly, but these will tend to be one-off fixes, often data deliverables, but not finished products . You will also gradually slip on testing, and QA in general. Working in an engineering team environment has all sorts of bene…
You're entirely right that you get used to delivering working solutions that are ultimately one-off fixes, but at the same time you also discover how to use technologies that speed up your production in a more pragmatic fashion. It's definitely not a product lifecycle, it's a project lifecycle – different but not any less valuable.
Although, it is unfortunate you have no coworkers. The thing I miss most about working at an agency is being able to poll my many developer colleagues to research and discover different approaches to problems. The fast pace of an agency often means that you aren't the first to discover a problem that occurs on a project, and your colleagues are a highly valuable commodity that you don't necessarily get at a product.
Earlier quoted context omitted.
Since there are no more upvote-points, we can't know how many people agree with the comment, so "this" are again required (or show alternative).
I do not need to know how many people agree with something to know whether I agree or disagree with it. There's no need to show upvote points; just order it so I'm more likely to read the things that other people think are worth reading. I can judge it myself without seeing N "this" comments or upvote points beside it.
I'm the only developer in my ad agency of about 80 people. It's super cool to write all my own code, make all my own stack choices. To know that I wrote everything here is a really cool feeling. At the same time, I really miss talking shop with other devs. And given my extremely young age (only a few years out of school) sometimes it can be hard to be sure I'm making the most efficient choices. There's a lot of times…
I'm the only developer in my ad agency of about 80 people. It's super cool to write all my own code, make all my own stack choices. To know that I wrote everything here is a really cool feeling. At the same time, I really miss talking shop with other devs. And given my extremely young age (only a few years out of school) sometimes it can be hard to be sure I'm making the most efficient choices. There's a lot of times…
I wish more people would understand this. If you are have one or two developers, you can not act like google. Management does not understand this.
I'm the only developer in my ad agency of about 80 people. It's super cool to write all my own code, make all my own stack choices. To know that I wrote everything here is a really cool feeling. At the same time, I really miss talking shop with other devs. And given my extremely young age (only a few years out of school) sometimes it can be hard to be sure I'm making the most efficient choices. There's a lot of times…
I did that for 4 years. Beware! Being the only tech at an "agency" will quickly atrophy your core engineering skills, if you're not careful. You will get _good_ at delivering working solutions quickly, but these will tend to be one-off fixes, often data deliverables, but not finished products . You will also gradually slip on testing, and QA in general. Working in an engineering team environment has all sorts of bene…
Most grunt work is automated and so much knowledge is leveraged even solo-shops can keep all tech together. Good! That said, data from hard-science problems is the new nut to crack. I almost cry thinking of startups like rescale.com, the chance they offer to independent researchers and scientists to do so much more than it can be done in a shared lab or cluster. When I read of $$$ burn rate in the SV, I cringe: one i…
Is rescale's offering the equivalent of an Ikea table? I'm not sure of the relevance of the connection.