Working

// I started a new job earlier this year, wow.

I thought I was with it, but then I found out I wasn't

So, earlier this year (March 2022), I started a new job. Same field (software development) but at a different company doing similar work, but with a new framework. It's a proper start-up, not like my previous company (and that's definitely a different blog post), so there's some long days, and crazy code (from the MVP).

While it's the same field, the work-place has a much nicer balance to it (while still kind of intense work-load wise). It's definitely a nicer environment to work in, and I think I'm actually getting almost my proper value. On that note, I often forget that I should always take a couple of steps back and look at the work I have typed out and done. I've powered companies from the ground up with the work I have done (from inductions to retirement in a single system for example).

It's nice to be appreciated. The pay also helps understand/comprehend that appreciation, and also aids in driving me to achieve more.

Programming is a lot like gardening

You reap what you sow. Evidence from the MVP shows that it grew really rapidly, but the proper care that should have been taken wasn't there (and there's a lack of comments explaining so). It's quite easy to see when looking at the code-base that there's a lot of inexperienced dev work done, and while it works, it was not working like a well oiled machine.

Not to shit on it entirely though, the documentation shits on what I came from (which was next to none, other than the KB I assisted with in the service/ops department, but I'll save that for another post).

Debt, it's technical

Working for a boss who isn't technical (software development wise) has it's perks, they don't know the limitations of what can and can't be done (easily) so they'll ask/want some outlandish things. --Working for a boss who isn't technical (software development wise) has it's cons, they don't know the limitations of what can and can't be done (easily) so they'll ask/want some outlandish things.

With that in mind though, the right approach can allow you as a developer to navigate the situation as both an advisor and technical liason. Your employer (hopefully) is reasonable enough that you can explain easy vs hard, simple and quick vs. complicated and hard. Remember, they just want the thing, and you shouldn't be quick to shoot them down, there may be a better solution to the problem, help them find it.

A couple of tricks I employ (one I picked up from an old collegue) are as follows.

1. Never say "no", at least not outright, a better answer is to confirm priorities, make sure they're aware of what would be bumped, or deadlines would have the potential of being missed. They may be a bit miffed at not getting what they want, but the end result is the same, they're trying to make a product, and you're trying to stay employed. If there's no product to sell, there's no company to pay you.
2. "Thats interesting" will save your behind more often than you think. Rather than calling out bullshit straight away, employ the functionality of a firm "hmm, that's interesting" and a pondering look. It does a few immediate things, mainly that you've acknowledged the question/statement, and that you've acknowledge the strange-ness. Handy for when "the screen is blank" or "printer wasn't working this morning" (we had a black-out), while keeping your internal voice safe from harms way.

I don't know where I was going with the above.

Making new friends

I tend to not make friends easily, I'm quite the recluse and quite guarded. I do give off "strange" vibes and don't actively engage in conversation. I can only assume that that doesn't make me the best collegue, or the worst for that matter. However, I do know that my work speaks for itself, and that it is appreciated by my collegues and out customers. Which is nice.