If you don't test for it the bug doesn't exist.

German public wifi reminds me of the Internet in early 90s 🤬😫😫😫🤯

messy backend API. root level payload object has a property that is being repeated in a property that takes an array of objects where this same property exists in each object in this array.

why do people work in a messy manner like this? why pass the same data twice in the exact same request?

(lead architect is smart, but holy fuck is his work a goddamn mess of technical debt and hurts my brain and productivity)

It would be nice and more community spirit if people on YouTube would:

- stop using A.I. for voice-over
- stop using A.I. for random comments
- stop using A.I. for video content

It's beginning to become confusing what's real and what's not. I admire real creators, not quick-buck fakers.

my scrum master keeps changing the format of retro and it works worse every time. We're at the 2.5 hour mark right now. It is aggressively hot and humid in the office. Everyone is asleep.

I don't think there's a way to explain to him that the purpose of a retro is not to magically fix things within the format but to financially commit to the preference for conversation, from which the hidden work of resolving conflicts can be billed.

Had a job interview 3 weeks ago, all went very well.

They asked me to do a dev task, I did it and delivered it the same day (simple task really)

Got no confirmation of receipt and eventually chased a week later and they confirmed they had it and would be in touch by that weekend. Another week beyond that passed and still nothing.

If the interview hadn’t gone as well I’d not be bothered but why the fuck do companies go as far as asking you to do a dev task to not communicate with you after that.

Tbh, ostream is a nice guy. Once you get over his

- Racism towards Germans
- Racism towards Jews
- Closeted racism towards anyone, really
- Psychotic episodes of rage
- Borderline criminal tendencies
- Bipolar disorder

It's actually fun to talk to him. You have to invest time and patience though.

Love you ostream bro.

Let's get ready for another rant. I work at a new company now which claims to be "fast paced" and startup-like culture. At the same time, I don't think I've ever seen a place with more rules and bureaucracy when it comes to engineering.

By the looks of it, my manager seems to value process a lot more than actual outcome. Both my manager and another engineer in the team tend to nitpick over every line of code and will not approve anything until they believe it's absolutely perfect and up to their liking.

Every PR I create has to go through 5 cycles of review. On top of that, the comments that get added are rarely related to product impact, but rateher "let's rename this variable in a test file to this", "maybe we should have this many spaces in a config file". There's been actual cases where I had to go through different cycles and had my PR's blocked for days because of some minor comments about variable names and styling they "liked" more.

This is one of the main reasons why we lose critical time during the development of our features. There seems to be no sense of priorities or urgency. The other reason we keep losing time is because of the massive amount of team meetings we have. Our team has only 3 engineers. How many meetings can you possibly schedule in a day to "realign". We have technical meetings where it apparentely is necessary to all agree on every tiny detail, such as which types we're gonna use etc etc.

That's not all. Last week, weeks of my work was thrown out of the window, because it was slightly different from how "we" usually do it. Even though, I explained and motivated how my solution solved issues the other proposed solution did not, we ended up spending an additional two days reimplementing the same fixes more in line with "the rules".

I recently reviewed a coworker's PR pointing out actual functionality that was not working as expected. Real user impact...
I created an alternative solution that covered all cases, and sent it. It got basically ignored. Then we ended up having a meeting for hours with several engineers where they made me watch how they started fixing the same issues as I had already fixed.

Each week, I'm losing around 2-3 days of development time dealing with this nonsense. But then there's a deadline. Then the manager goes full-on wild and pushes everyone into overtime and will send you 700 messages a day in channels or privately to you if "you need help" and how things should be done.

I'm not looking forward to switching jobs again, but please tell me... how can I cope with this?

Thanks

Driving data from your car (direction, Gs, cameras) can be used to estimate your “recklessness”, bought by banks and used to “properly evaluate” your insurance price 🙈

Company made it known a few weeks earlier they are not longer profitable...

Solution? Organize a table tennis tournament between colleagues. Mandatory participation.

Bunch of clowns

My company is making is sit through what can better be described as "The Dundees".
Those useless, time wasting, self aggrandizing "award cerimonies" that companies use to... dunno, I think to stroke management's ego.
I guess it's part of their compensation package, right there with making the hottest employees wear revealing clothing in order to be "engaged" in "informal team building exercises".
Frankly, I'm glad my sixteen-years-after-my-navy-days ass doesn't qualify.

Fuuuck, why can't they just give themselves bonuses for being "such engaging person-bosses" and let the rest of us just work? Corruption used to be a quick and easy affair. Now it requires soooo much fanfare.

It sucks that peripheral manufacturers don't fully support Linux. I've given Linux Mint an honest and fair try and I like it for being distraction-free and unbloated as opposed to Windows. However, there are too many things that don't work in Linux, such as connecting an external VGA screen through an HDMI adaptor, or to configure a Logitech mouse. It's a deal breaker.

I've started messing with C++ again, and it's kinda fun :)

I'm a fan of modular systems, so I've decided to build a little proof of concept for plugin loading.

A plugin is basically just a shared library which exposes a class that extends the Plugin abstract class and implements some lifecycle methods.

Then a plugin file has a system specific PLUGIN_EXPORT create_plugin()... function that just returns an instance of the plugin.

I've decided to use a super simple event bus for communicating from the host system to the plugin and vice versa, it's supplied in a PluginContext class which is supplied to the plugin upon initialisation.

Loading the plugins is done via LoadLibraryA(...) or dlopen(...).

Of course I'm freeing/closing them again at the end of the host system lifecycle. I hope to eventually implement some form of HMR.

Idunno why I'm sharing this; The system has zero purpose other than learning, but I've figured that implementing plugins in a "lower" level language, rather than typescript with node is more fun :)

Systemd has telemetry now!

If I publish this I'll have to credit chatgpt.

Bing, Google, and StackOverflow pushing users to use AI is like the vinyl and music industry pushing CDs in the 1990s. Like lemmings, rushing self-deprecation.

Manager: "add this"
Me: *adds the thing*

One week later:
Manager: "Remove this we don't want it anymore"
Me: Fuuuuuuuckkkkk

Has @Demolishun deactivated his account?

15+ years in the "industry" and I'm slowly losing my ability to be self motivated. I'm tired of the grind most days.

But any time someone comes to me with a problem they're stuck on, I'm instantly motivated.

Am I burnt out or just transitioning?

Overnight, our networking dept patched some systems, which unexpectedly caused a connecting system unable to work. That system was our alerting layer, which didn't/couldn't send out the alerts (phone calls, Teams messages, emails, etc) that alerting wasn't working.

This morning when networking came in, they saw the issue (our backup alerting system was sending emails all night long).

Instead of "Oh no, maybe we should have a process in place to verify patching X systems doesn't degrade Y systems", the various teams are dog-piling on alerting (my responsibility). VPs are now getting involved. They are saying things like "There should have been a monitoring system to monitor the alerting!!!". Which there is, the email back up alerting. Must be a dozens of messages in the team chat all pointing the finger that 'alerting should have worked', even though *those server clusters were all down*. My boss tried to chime in with common sense saying "If our infrastructure team can't guarantee 100% uptime on the clusters, then this will happen again. The issue happened once in the 5+ years we've been using this framework. We can spend time and money creating yet another monitoring system, which could fail too, or accept the reality that sometimes things break. We fix it and do what is reasonable so the issue doesn't happen again. In my opinion, paying for another solution isn't feasible in this situation."

Team chat is silent right now, but my spidey sense is tingling.