I still remember my first day on my first job very vividly.

I had just complted a test task where I had to add tag functionality to an anti-anonymous image-board clone the company made (it was called rep dot ly, pretty badass domain name, sad that it folded), whereas the guys, Paul and Danko, implemented a webcam integration, so that people could add cute photos to imageboard-esque threads.

And so, my first day was at a conference where they were presenting the project. I remember being very ashamed that I went to another job interview after I went to theirs, and how interesting was everything in the conference hall. I felt a huge imposter syndrome, heh.

Then, when I started working it was kind of back and forth. Of course, I was slower than the other guys and less well-versed in industrial practices, but ultimately what got me into trouble is my back-then passion for overengineering and not being able to deterime when a design of a feature is good enough. I was with the guys till the very end of that iteration of though.

Afterwards I made an appearance in banking software, only to make a glorious, but short-lived return to very, where my desire for overengineering, augmented by banking experience, essentially got me fired, because I got too defensive about some program that I made to interact with postgresql, which wasn't doing the thing I was requested to do. But I'm very glad that my second stint with gave me production experience with , that I managed to leverage by writing . It eventually landed me my first well-paid job.

These days, is more or less a one-person show, but if you need some software, drop them a line, they're really cool.

Sign in to participate in the conversation
Doma Social

Mastodon server of