3,104 karma · joined June 10, 2021
On a ROI and prioritization metrics I put myself first, co-workers second, product third, company bottom-line fourth. Part of putting myself first is delivering things mandated by management (so, you know, I don't get fired) which skews to product and company bottom-line, but things I do of my own volition is definitely not going to the bottom-line/product.
I am lucky I am not time tracked aggressively and that my immediate superior lets us work on things out of our own volition. The fact that some of the stuff I do benefits the company indirectly is secondary to my motivation to do it.
Not necessarily so I can work less (afterall there is always work to do as a developer). But so I don't get annoyed.
Usually that ends up saving time for the company, but not always.
https://github.com/jeanp413/open-remote-ssh
I run the editor (and its extensions), my projects and any agent harnesses from inside a container and use that extension to get an editor.
This is mostly to protect my credentials and data from malicious extensions/dependencies/rogue-agents, bu it also lets me quickly port my dev environment to any machine (I use linux at home and macos at work). Just install podman, install VSCodium, add the SSH extension, build image, add my utility shellscripts (to quickly get in and out of the container in a shell) and done.
Apparently Microsoft keep some VSCode APIs proprietary so only its own extensions can use it (allegedly for security reasons), which is why this specific extension only works in VSCodium. I wonder if it is vulnerable to the same things the article points out.
It is that grey zone where it is kinda worth it to pay someone to do it, but also might not be worth it the headaches of managing that person and the infra (like what happens if they go on vacation). The improved speed is the thing that tilts the balance.
It is more like looking at test diffs is more valuable than looking at new tests.
But yeah, I wish people would clean up LLM-slop a bit and remove some useless tests, but I think this status quo is actually better than no tests at all.
Somehow I remember those parts more than the fun parts, maybe because I didn't have access to a guide back then.
They would put up with crazy puzzles, huge grinds, weird RPG numbers systems (AD&D in BG1/2 for example), but if you want to do action A on thing B that can not, under any circumstance feel bad to do.
And that is just when you can talk to the engineers directly, it gets worse when you need to escalate on the management chain.
Startups are easier because most of the time you usually only need one rubberstamp (and sometimes none!) to do something.
It gets much worse though once the startup scales up and becomes massive. Then it tends to be worse than big corps because there at least they have processes.
The work was essentially web scraping complex systems, which is not a case of "you don't need someone with my experience to do this" and more like I just didn't want to do it because it did not improve my current skills at all.
It is not like in the interview they told me: you will be doing web scraping for months on end. Or that I even thought to ask.
Thing is I bet the people who played it are right too, I just never managed to bring myself to play more than a few hours of the game before getting frustrated. Bad controls + 90s point-and-click-puzzle-design + early 3d graphics is not a good recipe.
Full Throttle was criticized for its dumbed-down point-and-click (basic only 3 actions + using items, instead of the usual verbs), but that was the sweetspot for my early-teens mind. Can never get enough funny responses of using the lick action.
At least 3 times last month I was asked to review a change in a .md file used by agents. And I am like: "yeah I guess it makes sense?"
It feels we need to write unit tests for this stuff, but even how to do so in reasonable time and complexity seems difficult.
Also some shares pay dividends.
Even if you agree with the former exploiting the commons for personal profit is... not good.
One could make the argument that if these LLMs were all open weight it would be okay, but to keep the result of the training private and proprietary is not fair.
Never thought I would say the day, when I joined this career all I wanted was to work on interesting problems and not work more than 40 hours per week. These days the interesting problems are always solved in the worse ways possible and I am often swamped with work that I don't even have the time to do any improvements out of my personally-assigned backlog.
With the compilation making use of the native instruction set supported for your device, so it can make use of newer arm instructions on newer devices while still supporting older devices.
This is the major reason app installation is so slow in Android compared to iOS (which pre-compiles everything). But it also greatly improves app compatibility with older versions.
There is no way Valve would be able to convince all the myriad of game engine developers to support a proprietary (or even open source) bytecode format even in the future. Best they could do is make it an opt-in.
Android only pulled it off because Google provides the "engine" (Android SDK) for all apps made for the platform and it did from the start.
And even so, most Androids games actually bypass this system entirely and just hand-compile to native binaries anyway. Because, again, the game engines don't want to support this bytecode format and google doesn't offer a C++ toolchain themselves that the engine developers could integrate with.
I was about to say that, don't forget your cache-control headers kids.
Also in my experience lower pay places tend to eventually suck because they tend to get into financial difficulties much more easily.
At my current place (apartment in a suburb about 10km from the city center) our parking would cost ~180 USD per month. From a tech worker perspective it is not like unaffordable, but definetily a luxury for most of the population. The median after-tax income in Sweden is like 3k USD.
That tax I mentioned before also makes very old beat-up cars not worth keeping (which is the intent of the tax to be fair).
One of the main upsides of living in a detached house in Sweden is not having to pay for parking. But even so the increase heating bills in winter can easily cost more than a car installment depending on your HVAC and insulation.
C# LINQ also seem to be the best compromise between ORM and raw SQL queries, although I never used it myself.
I have been severely disappointed in all similar solutions for Go at least and I imagine Rust does not have something better given it has a smaller community-base.
Python and NodeJS have some very neat solutions for this stuff too, but both are "slow" dynamic languages. I personally dislike python with a passion and NodeJS stuff is extremely community-driven and therefor often unreliable. Prisma (NodeJS ORM) for example just did a major overhaul and is now pushing a completely different API.
If you are making boring REST API to SQL Database it seems like Java and C# are the best options.
For the company yes, not for the executive bonuses.
It is quite notable how the long-lasting companies that are household names somehow managed to resist this urge. Most of them are private.
People need to compartmentalize things in order to make sense of the universe, but doing so for companies (and governments) is just counterproductive.
Whenever you think about a company to draw any good conclusions you always need to think about all the people who work there, from the factory worker to the executive.
I just made a bash script that shells into the container (or starts it if it is not already running) and in there everything is set up.
Even if you are not unionized you benefit from other people being unionized in your profession/area.
MGSV Metal Gear Online (the _other_ tacked-on multiplayer) was also great, but very unreliable netcode made it frustrating.
I wish someone would just take that game engine and make another good game on it. I _almost_ bought metal gear survive on the engine alone, that is how good it is.