A rather droll article that skips the interesting part of describing the journey and instead just states the origin and destination.
What did stand out though…
It was started by members of our development team and is written in Scala, which isn’t well known as a systems language. We were lucky enough to have a member of the operations team with a background in development who was keen to learn and took over leading its direction.
This screams of developers trying to make problems more interesting than they are.
Decision to adopt new process, but “hell, lobbying colleagues is hard…I just want to code” - check
Writing from scratch rather than improving an existing product where resourcing skills could be obtained - check
Pick a language that looks sexy, new and not shared by all members of the team who have to maintain it plus to boot make hiring harder - check
Over time tire of the problem space and do a code drop onto the sysadmin team - check
Maybe this is a mis-interpretation on my part, not helped by the article skipping the interesting hard social changes, but I am not convinced as…
We eventually decided to start work on the tooling anyway.
Christ on a bike. Programming as a hobby and programming as a job are very different things. One is called “work” for a reason after all.
How I tackle problems that are my hobbies is so different to how I do so for my clients. Maybe I would prototype to see if we got superpowers by using a particular new-to-us combination of technologies, but the lobbying step is so crucial it is simply irresponsible and straight up rude to not do so.
Eugh, now I have to go back to writing PHP/JavaScript/Python, as awful as it for me, it communicates ideas to everyone in my audience.
A rather droll article that skips the interesting part of describing the journey and instead just states the origin and destination.
What did stand out though…
This screams of developers trying to make problems more interesting than they are.
Maybe this is a mis-interpretation on my part, not helped by the article skipping the interesting hard social changes, but I am not convinced as…
Christ on a bike. Programming as a hobby and programming as a job are very different things. One is called “work” for a reason after all.
How I tackle problems that are my hobbies is so different to how I do so for my clients. Maybe I would prototype to see if we got superpowers by using a particular new-to-us combination of technologies, but the lobbying step is so crucial it is simply irresponsible and straight up rude to not do so.
Eugh, now I have to go back to writing PHP/JavaScript/Python, as awful as it for me, it communicates ideas to everyone in my audience.