a1studmuffin

I quite liked the concept a few years back when Apple and Google were talking about a Netflix-style subscription model for iOS/Android… a bit like Xbox Game Pass. The subscription would give you access to a bunch of games, and developers were paid royalties based on a mix of metrics like the game review score, number of downloads, average total time spent in game etc. It seemed like a good idea in that it aligned developers and players in the desire for genuinely good games, regardless of the game style or genre. It threw away the need for each game to find a way to monetize their players (which nearly always ends up in multiplayer endless cosmetic MTX nonsense).

Janitor.

I remember installing a keylogger on the school library computers, then “accidentally” disconnecting the dialup internet and asking the teacher to type the login credentials again. I bet the ISP was confused when they saw so many concurrent logins after hours, all playing Quake and downloading huge files.

C/C++ still has a huge place in firmware, microcontrollers, operating systems, drivers, application development, video games, real-time systems and so on. It’s a totally different space of programming to webdev, which might explain the surprise.

Sometimes the real value of a project isn’t its proposed worth, but the schadenfreude it offers instead. I’ve backed a few failed Kickstarters that I absolutely got my money’s worth on.

It sounds like you’re in the right area by focusing on C. Have you got a GitHub profile? I’d start looking for open source projects in that space and get involved. Many of them have beginner bugs and tasks. Some projects are better than others at welcoming juniors, so check their readme to see if they have any advice.

If you’re interested in low-level languages like C and C++, I would take a look at Rust. It’s another performance-focused language that complies to assembler like C, but includes some clever design principles to prevent a lot of common C/C++ bugs from being possible at all. Even if you don’t end up using it much, it’s quite interesting to see a different way of thinking about things to achieve a similar output.

Beyond that, I’d say you need to think about the job opportunities you’re interested in and learn what tech they use.

If you’re concerned about privacy I don’t know why you’d use Tailscale over Wireguard directly. The latter is slightly more fiddly to configure, but you only do it once and there’s no cloud middleman involved, just your devices talking directly to each other.

Clearly we’re going to need regulations around personal vehicle size limits on the road. If you legitimately need a big truck for your business, get a licence for it.

I’d recommend setting up a GitHub profile and developing some personal projects on there, and try to get some experience contributing to other projects (even if they’re just simple first PRs). Make sure you include this on your resume, it’s a great talking point for juniors to show you’re passionate and have concrete examples of your code in the wild.

Also set up a LinkedIn profile (fleshed out as best you can) and start adding people at companies you’re interested in. DM them asking for advice, most people are lovely and want to help. While LinkedIn is horrible and needs to die, it’s still used heavily by the tech industry and you’ll find every tech company and recruiters on there.

You know it’s bad when we’re having to invent new words like ‘polycrisis’ to succinctly describe what’s happening.

… or worked in a large team with juniors and members coming and going over a long period of time.

To take up a career in programming is to be professionally confused on a day-to-day basis. It’s normal to feel overwhelmed at times, but this is the advice I give younger engineers: accept that confusion, and try to channel it into curiosity instead of letting it fester into stress and anxiety.

Horizon Zero Mean Girls

I’d rather drink a verification can every 30 minutes.

Smells like something IDF unit 8200 might have been involved with.

This has been the weirdest console generation. I’m still surprised they railroaded ahead with the PS5 and Xbox Series X launches right at the beginning of the pandemic.

It’s the same for people who don’t understand basic electronics or mechanics. Any problem just becomes “it’s broken” and the only solution is to take it to an expert and pay for their time, or toss it and buy a new one. It’s expensive to be ignorant.

To kill any competition and ensure they retain control over future standards. Money. It’s pretty straightforward.

The basic idea is that a huge company with infinite money creates software that supports an open standard, such as Threads. Next they spend significant amounts of money driving users to their software, rather than an open software equivalent. Once they’ve captured a huge percent of all users of the open standard, they abandon the open standard, going with a proprietary one instead. They’ll make up some new feature to justify this and sell it as a positive. Because they control almost all of the users at this point, many of the users they don’t control will decide to switch over to their software, otherwise the value of the open standard drops significantly overnight for them. What’s left is a “dead” open standard that still technically exists but is no longer used. You can find plenty of past examples of this pattern, such as Google and XMPP.