5 ms·
In a similar vein, picking one true way forward from a collection of similar options helps keep engineers productive as they move between components. I am a st
by twic 10y ago
In a similar vein, picking one true way forward from a collection of similar options helps keep engineers productive as they move between components.
I am a strong believer in this. However, i believe it's a wildly unfashionable idea in this day and age, where developer autonomy, 'best tool for the job', and polyglossia are the in things. I was interested to see it in this otherwise pretty hip and happening list.
The idea was that making coffee would be five to ten minute process, during which there would be time to interact with colleagues who happened to drop by the area. The system worked.
There's a similar meme in medical research institutes (at least, the ones i've worked in), which was popularised by the Laboratory for Molecular Biology:
http://www.insight.mrc.ac.uk/2013/06/06/the-great-coffee-breakthrough/ http://www.insight.mrc.ac.uk/2013/06/06/the-great-coffee-bre...
If an engineer needed a new resource for a service being deployed, prototype, or even one-off experiment, they were at liberty to provision it and keep on working, even if that resource wasn’t free. Resources here might include everything from dynos to run an app, to a Postgres backend, to a few extra EC2 boxes for deployment to bare metal (relatively speaking).
I've come across this "self service" idea as a selling point for internal platforms and PaaS, but there seems to be a small but important difference - with a platform, developers can self-service anything that is part of the platform, whereas it sounds like at Heroku, it was anything - full stop. Although, as the author mentions, the fact that they were on AWS meant that that was ultimately still on a platform. Anyway, that difference can matter if there are things that aren't on the platform - if you're using Cloud Foundry, for instance, then you won't be able to self-service persistent disks, network configuration, or anything else at that level, which means that in practice, there is considerable drag from interacting with other teams to get that stuff provisioned. A radical commitment to self-service would be interesting to see.
But although technical management wasn’t an idea that lasted, it was a very good place to be an engineer while it did.
One of the genius things i learned at Pivotal was that a 'team lead' and a 'manager' don't have to be the same person, and that neither of them has to be a 'boss'. Every developer needs a 'team lead' (in Pivotal cant, 'anchor') to lead the day-to-day operation of a development team, and a 'manager' to channel feedback, guide career progression, ensure happiness, etc, but they it's better if they're separate people, and it's better if they're drawn from the ranks of the developer's peers (albeit the more senior ones), rather than being some formally separate layer of the organisation. You should always have technical leadership; you should usually have technical management too, although it probably makes sense for the most senior technical-management people to have non-technical managers themselves.
- nfriedly 10y ago> 'team lead' and a 'manager' don't have to be the same person This has been my experience at several places I've worked, including my current work at IBM Watson. I talk to my manager maybe once a month at best[1], whereas the team lead is doing the same work as the rest of the team and in communication with the other members almost every day. [1]: this is partially because I work remote - I assume I'd speak to my manager a little more often if we worked in close proximity.
- eikenberry 10y agoI don't think the "best tool for the job" necessitates needless polyglossia. They obviously have a "best tool for the job" mentality to some extent as they have 3 official/primary languages, not 1 like some places I've worked. How many different languages/technologies are required for it to qualify as polyglossia?
- twic 10y agoOne more than however many I personally know, of course :). I suppose the only defensible definition of the term would be more than one language, with some qualifier like "for any given context", because using C++ to serve your JavaScript app isn't polyglot. But then we just argue about how big a context is - are API servers and systems of record the same context? A more fruitful perspective might be to look at how the decision to adopt a new language etc is made. If an individual developer can do it, it's a potentially polyglot environment, whether that potential has been realised or not. If it requires an organisation-wide process (whether CTO decree or consensus at an all-hands meeting), it's unlikely to be a polyglot environment. This perspective is definitely a product of my own particular experiences, though, and might not be generally relevant.
- kelnos 10y agoI'm very torn on the polyglot topic. Adding just one additional framework, library, or language that performs a similar function to what's already used can add a huge burden on a mature organization. You end up with so much tooling around what you're using, that adding something new means your system is much less robust than if you'd stuck to the things the rest of your org uses. At the same time, using the same stuff leads to a stagnant stack: it makes it harder to hire and retain, and you miss out on some genuinely better ways of doing things. A "do whatever you want" policy is destined to fail, but being to strict and disallowing experimentation isn't the answer either, and I struggle to find where the balance should be.