Want to make someone's life a misery? Here's how.

Don't base your tech stack on any prior knowledge or what's relevant to the problem.

Instead design it around all the latest trends and badges you want to put on your resume because they're frequent key words on job postings.

Once your data goes in, you'll never get it out again. At best you'll be teased with little crumbs of data but never the whole.

I know, here's a genius idea, instead of putting data into a normal data base then using a cache, lets put it all into the cache and by the way it's a volatile cache.

Here's an idea. For something as simple as a single log lets make it use a queue that goes into a queue that goes into another queue that goes into another queue all of which are black boxes. No rhyme of reason, queues are all the rage.

Have you tried: Lets use a new fangled tangle, trust me it's safe, INSERT BIG NAME HERE uses it.

Finally it all gets flushed down into this subterranean cunt of a sewerage system and good luck getting it all out again. It's like hell except it's all shitty instead of all fiery.

All I want is to export one table, a simple log table with a few GB to CSV or heck whatever generic format it supports, that's it.

So I run the export table to file command and off it goes only less than a minute later for timeout commands to start piling up until it aborts. WTF. So then I set the most obvious timeout setting in the client, no change, then another timeout setting on the client, no change, then i try to put it in the client configuration file, no change, then I set the timeout on the export query, no change, then finally I bump the timeouts in the server config, no change, then I find someone has downloaded it from both tucows and apt, but they're using the tucows version so its real config is in /dev/database.xml (don't even ask). I increase that from seconds to a minute, it's still timing out after a minute.

In the end I have to make my own and this involves working out how to parse non-standard binary formatted data structures. It's the umpteenth time I have had to do this.

These aren't some no name solutions and it really terrifies me. All this is doing is taking some access logs, store them in one place then index by timestamp. These things are all meant to be blazing fast but grep is often faster. How the hell is such a trivial thing turned into a series of one nightmare after another? Things that should take a few minutes take days of screwing around. I don't have access logs any more because I can't access them anymore.

The terror of this isn't that it's so awful, it's that all the little kiddies doing all this jazz for the first time and using all these shit wipe buzzword driven approaches have no fucking clue it's not meant to be this difficult. I'm replacing entire tens of thousands to million line enterprise systems with a few hundred lines of code that's faster, more reliable and better in virtually every measurable way time and time again.

This is constant. It's not one offender, it's not one project, it's not one company, it's not one developer, it's the industry standard. It's all over open source software and all over dev shops. Everything is exponentially becoming more bloated and difficult than it needs to be. I'm seeing people pull up a hundred cloud instances for things that'll be happy at home with a few minutes to a week's optimisation efforts. Queries that are N*N and only take a few minutes to turn to LOG(N) but instead people renting out a fucking off huge ass SQL cluster instead that not only costs gobs of money but takes a ton of time maintaining and configuring which isn't going to be done right either.

I think most people are bullshitting when they say they have impostor syndrome but when the trend in technology is to make every fucking little trivial thing a thousand times more complex than it has to be I can see how they'd feel that way. There's so bloody much you need to do that you don't need to do these days that you either can't get anything done right or the smallest thing takes an age.

I have no idea why some people put up with some of these appliances. If you bought a dish washer that made washing dishes even harder than it was before you'd return it to the store.

Every time I see the terms enterprise, fast, big data, scalable, cloud or anything of the like I bang my head on the table. One of these days I'm going to lose my fucking tits.

So I'm starting a job at a large company in the early part of next year... it's a total mindfuck because the salary is a m a s s i v e bump up and for the first time I'm experiencing imposter syndrome. I never really fully grasped the feeling that a lot of people here described until after that final interview and an offer was extended. I'm stoked AF to start and it's going to be a huge learning experience while working there.

The company wants me and my family to relocate to another state (US) and it's got my stomach doing somersalts.

It's especially painful because the current place I'm working is amazing; the people are great, the work is solid but fairly low pressure, and there's lateral freedom to work on improving the systems and infrastructure whenever there is free time. And I know that the new gig is going to have certain expectations that need to be met or my head could be on the chopping block.

High risk, high reward I guess 😅

My anxiety is raw dogging my brain and it fucking sucks, but my wife has been doing a great job keeping me level headed and thinking logically about the future and growth this opportunity brings with it.

I'm not trying to gloat or brag, just really needed a place to share some of this since I'm freaking out and don't feel like I have enough experience/skills to take on this job. Those interviews left me worn out. 4 rounds and the final interview was 5 hours long all in one day. 😫

After all those years, I finally understood what makes Half-Life 2 so immersive.

From the very beginning, as the game teaches you things about itself, you discover that every model is made with you in mind. The barrel is just tall enough to jump on it, but not taller. The big crate's size is calculated precisely for you to jump onto it from a small crate. Ladders are comfortable for you to climb on. Everything in this game world designed around you, the human.

…except for combine constructions.

They're awkward to walk around. You keep lowkey clipping into them. Half-transparent armor fence looks like you can jump over it, but you can't. It's just a bit taller than that, on purpose. Combine towers are hard to climb onto. You keep bumping into things. Once you locate the ladder and climb all the way up, you bump your head into the ceiling. You don't have much room for movement on top. Combine walls have an inconclusive, uncomfortable physics model that is very annoying to interact with. If you run into it and jump, you clip into it just enough to stop your movement instantly.

This hammers in the message — combines aren't human. Their constructions aren't meant for humans. This was my biggest discovery the last time I played Half-Life 2.

HL2 is a strong contender to be my favorite game of all time.

#just Bluetooth headphones things

When you're sitting on crowded public transportation and can't hear anything unless your phone is closer to your headphones than anyone else's, i.e. unless it's close as shit to your face 😍😍😍

When you want to listen to music for longer than 2 hours or several times during your workday but can't because the BT headphones last 2-3 hours 😍😍😍

When the left and right side don't pair with each other but you can pair with each individually 😍😍😍

When half of the button presses and user interactions aren't documented and there's no way to forget a device 😍😍😍

When you try to connect a new device to them in a public area and just see a dozen random serial numbers, so you have to wait and hope they get resolved to the headphone brand name 😍😍😍

When Satan takes your soul and the Bluetooth connection drops in hell 😍😍😍

When the music quality is lower and can experience static and maybe even skip in between 😍😍😍

When the bus hits a road bump, it falls out of your ear, and rolls halfway down the bus 😍😍😍

When it takes a long time to find them because they tiny af, and just as long to find the charging cable 😍😍😍

When manufacturers cannot agree on a standard volume sync system and so you have to check the volume and adjust every time you connect and disconnect your headphones 😍😍😍

Can we please just stop making everything Bluetooth?

Sincerely,
Someone who just wanted to listen to a 2 minute billie eilish song but found it easier to sing in his head

Wrapping up at the end of the day, telling my colleague we can pick the rest of the task when we return on Monday..........only to find out we ARE Monday

Not sure where I hit my head today, but holy shit it sucks.

T-4 I guess

Question about managing git branches.

For releases, we branch develop (the main branch) into a release.version branch in which we bump the version and do any last minute bug fixes for issues found in testing.

After the release we need it back into the main branch as well as master.

But also we keep the branch as well in case we need it such as for a hotfix release.

Is keeping it right though?

General issue on my team I feel is nobody deletes their feature branches after they are done and merged into the main branch. I think there is a feature in most Repos where it can auto delete these branches when a PR is merged.

And well branches themselves (at least the HEAD) are sort of just bookmarks. All commits can be accessed by their hash and basically is a full snapshot of all the commits that upto that point that it was based off of?

So you could just tag the last commit in the release branch with release.version and delete the branch itself? And that I think is the correct, normal way?

Not sure how to explain this to my boss or team as they aren't big on technical details...