We have jestdotty, but where are chaidotty and mochadotty?

Bought a brand new Asus Laptop for my studies, because according to my asshat teacher "nobody is using a MacBook these days"...

After 2 minutes I wanted to punch a hole through the screen and my teacher's face.

Everything I fucking opened stopped responding

I hate windows

Had 1 beer in a pub. Had difficulty walking back to hotel.

You can tell I'm not a big drinker.
2 more weeks to pass here, in Dublin. And not get run over while crossing a street [u know, opposite traffic].

Somehow...

All for the sake of that promising project.

Back from Alpine to Debian as my daily driver. Here are the reasons:
1. Alpine doesn't support a very niche fan control utility made by one guy for my specific laptop, and HP left me with no alternative
2. Alpine doesn't have OpenSnitch, period
3. My laptop is quire powerful, so the speed difference is insignificant.

If it wasn't for this two super specific edge cases, I would've stayed on Alpine --- such a marvellous OS it was.

Management has reviewed DevOps which is already being shown to customers and wants to introduce a code coverage metric to show customers how good the code is. Code coverage now has to be 80% or higher across the board, it's been decided by management, and there is no discussion on this topic. The front-end presentation layer has minimal business logic and most of the code that exists is generated objects to shift data to the backend (which in turn mostly shifts it to a 3rd party API that does a lot of the business logic). I now have to write thousands of pointless tests while also being 85% billable to the client.
I think code coverage can be used as a tool, but should not be used as a metric to promote the product.
I suggested an automated e2e test might be better placed to prove that things are working, but have been told we're not going in that direction.
I'm close to writing a code coverage test that uses reflection to touch all of the code, catch all exceptions, and return a positive result.

why... WHY do I always attract all sorts of weird problems...

I feel like it makes me look incompetent :/

Like this side-gig. I had a client who brought us essentially half a rack (20 blade servers, 7 units of network equipment) and asked us to spin it up. No passwords, no topology - nothing. It was my first such "project".

So I'm setting it all up, using chatgpt and notions of vlan theory from college years ago. I managed to make smth work. Went away for the rest of the day. Hours later I come back -- no longer can connect to ovpn running on a MikroTik router. wtf... connect to office router's vpn, winbox via mac to the router to see wtf. Everything seems alright, except when I try to `/ip route print` it just hangs there. Tried a few times. -- same result. As if routes just got borked while noone was touching it. Found someone who's working with networks wtf, he said he's NEVER seen this happening. A router reboot sorted this out. That's weird problem #1.

I finished reverse-engineering and re-setting up the networking, sketched a topology with patching scheme and asked colleagues to take it all to the DC. They did it, connected it all up. 5 nodes aren't accessible via network. So I connect remotely to the router's openvpn and try to see what's up. Indeed, some servers are reachable, others aren't; even though MT switch (router's downlink) sees those servers plugged in with link up, servers don't see the link. I noticed some ports aren't trunking some VLANs. I started adding those ports when the winbox connection dropped out of the blue. 5-4-3-2-1-reconnecting... it reconnected. Yayy!! But wait, where is everything...? All interfaces -- gone (physical ones too). All IPs -- gone. All routes -- gone. Everything's gone. Half a minute later I'm disconnected again. The switch IP is no longer pingable. Servers plugged into it aren't reachable either. That's weird problem #2.

Then I figured I might try to see whether I can see anything from the router level. Try to ssh to it -- attempt was dropped, as if 22/tcp was closed. wtf? It was working in the office. winbox into it -- yayy, that works. Try to open a terminal via winbox -- a dialog pops up "Terminal <1> - not permitted (9)". wtf..? I Google this error up, it says that user is a member of group that does not have telnet and ssh permission. Indeed, I loog into groups -- the group 'admin' does not have them. Try to add them -- also not permitted. And I'm the 'admin' user, a single user in the router after a factory reset. How the hell else do I change permissions if even admin is flipped a finger.
That's weird problem #3

And now I look like an incompetent prick with two left hands who is only breaking shit.
And it's been like that my whole career

Why... How... ffs, that's getting annoying. Maybe I should downgrade myself to a QA. Problems find me themselves, I don't even have to look for them

The most interesting thing about the GDPR training that we do is that very little of it is about our rights as employees and almost all of it is to protect our employer. Funny that.

TIL: mechanical click of a touchpad is now managed by os in new lenovos. Suspend os and you can no longer click your touchpad.

Not tap. Click.

Wtf..

In my company I now have 3 browsers.

Chrome for company stuff that only works in Chrome.

Safari for company stuff that only works in Edge or Safari.

And Firefox for actual work.

🤡