Writing more infrastructure than product.

Look, my application requests and transforms data from a single external API endpoint, it's just one GET request...

But I made an intelligent response caching middleware to prevent downtime when the parent API goes down, I made mocks and tests for everything, the documentation is directly generated from the code and automatically hosted for every git branch using hooks, responses are translated into JSONschema notation which automatically generate integration tests on commit, and the transformations are set up as a modular collection of composable higher order lenses!

Boss: Please use less amphetamine.

XD

😂 Can you move to Germany? We're hiring and I want you.

@Divisionbyzero You're a recruiter, aren't you? I'm on to you...

@bittersweet I am an occupational therapist. We are working with persons with mental disorders. Your tasks wouldn't be IT related. And maybe your skills were useless, but I would be always in good mood with you. The payment sucks, too. But we have a lot of fun.

@AlexDeLarge Certainly not... communication and syncing up in development style, both intra- and inter-company, is maybe one of the most important activities for devs.

If everyone minds their own business, learning would be a really painful and lonely process.

And yeah, I should tone things down sometimes, but I just love getting lost in finding out how to build things, without actually fully building them.

Luckily, the company I work for has grown from 4 devs to about 120 devs, so I do have some space to experiment and tune.

I think there are "green-diff" devs who love writing a hundred models and controllers in three hours time, and "red-diff" devs who clean up & refactor the splinters left behind, experiment with abstraction, optimizations and stronger foundations.

I clearly belong in the latter category, and I do keep trying to put down sensible safeguards and tests so the green-differs can fly off at lightspeed with the right tools in their belt.