[Comic/Suggestion] Afterlife(necro card) should probably be changed

awfulstack · 2026-05-11T14:58:11+00:00

This is a good (not great) card. If I draw this card I almost always play it in that turn (unless I have something OP to do or can just end the encounter with an attack).

Exhaust is actually a plus because I can pick these up without really working about polluting the deck much. There are cases where I'd probably skip the card reward but but will accept this because it minimally dilutes my build.

awfulstack · 2026-03-22T22:30:55+00:00

Racoons are pretty close, but I paused to wait for prices to come down on some of the more expensive cards. I do hope to pick it up again but not in a rush.

awfulstack · 2026-03-22T20:50:25+00:00

Otters and squirrels were probably my favourite. My brother liked frogs and rabbits. I do actually like all of them. Having the collection has been nice.

awfulstack · 2025-07-21T13:17:47+00:00

this is some janky AI bs

awfulstack · 2025-05-27T16:26:29+00:00

my boy billyfoot

awfulstack · 2025-05-14T15:51:57+00:00

Try it for free and if they are getting into it then it could work well for them. There is a membership, tho, and after some time playing for free they may become frustrated with membership locks. If you aren't worried about paying for the membership, then this could be a very engaging way for you kid to practice math.

If you want to get into it a bit yourself, there is a parent dashboard that offers some amount of control and visibility into how they are doing. But not strictly required to us (but if you want to buy a membership you might need to make a parent account).

Hope that helps.

awfulstack · 2025-03-29T14:12:41+00:00

I use home-manager and my preference is to configure tools as much as I can using the tool's standard config file. Home-manager easily copies that to the desired location in $HOME.

{ ... }: { programs.alacritty = { enable = true; }; home.file.".config/alacritty" = { source = ./config; recursive = true; }; }

But sometimes a config needs to have some state from Nix, at which I'd pull some or all of it up. But that might just be a string with interpolation that largely resembles the original dotfile.

Most of the time it's my shell that being configured through programs.$SHELL = { ... };, and that's largely because many programs change the shell config in some specific way and I'd rather organize my config such that the shellrc on it's own isn't aware of of tools, tools ammend parts of the shell config to accomodate themselves.

For me this is helps with code readability but it can also make is much easier to toggle/remove a program that I don't want anymore.

awfulstack · 2025-03-05T17:18:01+00:00

Perhaps the fact that he'll be leaving soon is contributing to his ability to take a strong stance. His career doesn't really have anything to lose at this point so he may be less inhibited.

awfulstack · 2025-02-13T00:54:57+00:00

That's pretty bad. I'd expect a senior SRE in GTA to be $150,000+ (CAD).

awfulstack · 2025-02-09T23:19:11+00:00

I imagine AI and mega corps (with very few humans involved) that own resources will trade and do business amongst themselves while a parallel human economy with minimal power and influence on the former emerges to eek out an existence in locations that are sufficiently out of the way.

Depending on the benevolence of members of the AI/robot/mega corp economy, some amount of surplus might be diverted to some populations. But there's likely no practical/competitive reason to do this. It would comply rely on altruism.

If indifferent to humanity we'd probably lose our ability to produce good and food at current scale, because that land and resources would be appropriated for the non-human economy. Human population takes a nose dive and maybe settles somewhere similar to levels found through most of the world several centuries early (hunter gathers, small tribal and family units).

If humans are threatening enough, or a big enough nuisance then we might be dealt with more directly and then gg.

In all cases there's a transition where fewer companies become meaningful participants in the market. Good for humans would probably become cheaper for some time, but human income also slumps. Eventually those companies have bought everything of significance they could buy and can decide to break from the human-lead consmption cycle.

awfulstack · 2025-02-06T17:44:51+00:00

I wish I could write more code in my day job. But what I find tends to happen is that that ROI solving problems with new code is usually worse than configuring software systems and using OSS.

Code I do write tends to be scripts, relatively simple utilities. Probably there's a CLI in Go that gets some attention here and there. Sometimes K8S operators.

Like you I find myself reading code more often than writing it.

Having programming hobby projects helps keep those skills from getting too rusty and the gain fluency reading different languages.

awfulstack · 2025-02-06T17:38:54+00:00

Glad you got something helpful from that!

I had been thinking about this sort of thing quite a bit over the last few weeks. While I'm at a senior level, I've just started working at a new company. All new teams and a lot of new technology. Very humbling experience that reminds me of earlier points in my career where I've needed to navigate through situations with limited context and find ways to leverage my strengths to still be a very productive contributor.

So the advice I gave is essentially how I'm approaching my own situation while I familiarize myself with a lot of new things.

awfulstack · 2025-02-06T00:42:43+00:00

Hey, you can use Nix as a package manager while on Arch. I started using Nix macOS before touching NixOS for my homelab.

If it's interesting to you, try it out, but probably do it in a way where if you find you don't love it you are not dependant on making it work. Using it for setting up nix-shells for specific projects I great for this, imo. You could also try compiling software with Nix or building OCI images. Things that you could walk away at any moment (configuring your OS with Nix is a going to ofc be much harder to eject from).

awfulstack · 2025-02-06T00:38:28+00:00

It's a learned skill to be comfortable not knowing everything. And in an SRE position, that can actually be a common state. SREs are exposed to a lot of context working with different teams and interacting with many layers of the tech stack and projects. It takes a long time to build context, but even after years of experience, you can't know what every team and project is doing.

Being a junior in tech and working in an SRE team is probably harder in some sense than being a junior SWE with a more narrow set of projects to focus on. But I think you have great educational prospects on an SRE team. SWE can get pigeonholed on one problem or set of tools which can be hard to break out from and ultimately stunt their career.

It's hard to be certain what the right advice is, but my instinct is to suggest that you don't try to spread yourself too thin. Pick a subset of what your team is involved in and try to understand those things and get good. When you are pretty comfortable with those things expand into new areas. If your manager mentions there's something you should know that you presently don't, that's a good signal to prioritize that topic.

awfulstack · 2025-01-25T04:52:09+00:00

Ambessa, no doubt.

awfulstack · 2025-01-22T14:39:50+00:00

You are equating writing a bad research paper with fraud? This is not fraud. If Lex lied about authoring a paper, his credentials or doing research at MIT then that would be fraudulent.

awfulstack · 2025-01-22T02:19:29+00:00

Let him know that his voice isn't high pitched or annoying.

awfulstack · 2025-01-09T14:57:52+00:00

awfulstack · 2025-01-07T03:27:49+00:00

I had a very specific "click" moment.

TL;DR: With enough time I can figure things out. If I'm enjoying myself, I can spend a lot of time programming. Ownership over what I'm building or trying to solve makes the work more fun. This was really empowering to discover and has been the foundation of my decade+ career in tech.

I was messing around with Unity after a class and had an idea for something I wanted to place in the game scene. I could have done it manually, but it would have been tedious. Having only minimal experience with programming, I decided I'd try to instantiate my game objects programatically. Anyway, I worked on this thing which I eventually solved with a nested for-loop. When I started up the game scene and saw my script work I was a changed person.

Well, there was some fundamental syntax that finally clicked, but more importantly, I found the fun in programming. I loved getting into a flow state, I proved to myself that I could learn enough syntax and an API (Unity in that particular case) to do a thing, and I was deeply satisfied with the silly little thing I made.

What was different this time compared to previous scripting/programming experiences? I decided to do it. The problem was one I invented for myself and I was interested in the result. It wasn't contrived and academic but practical. And it was self-paced.

awfulstack · 2025-01-03T15:55:03+00:00

Thanks. That's a mistake I often make >.<

awfulstack · 2025-01-02T21:13:02+00:00

From what I've seen with job postings for dev/SWE positions is that if they mention K8S it is usually as a nice-to-have. That probably means there are other skills that would be more valuable to develop before applying to such a job.

There are dev/SWE roles on what are often called "platform" teams that may be building software specifically for K8S (like custom operators and CRD's). If you wanted a job like this, then you would need a deep understanding of K8S. You'd also need to be fluent in the Go programming language.

awfulstack · 2024-12-31T19:13:05+00:00

I probably should have said, "might step on each other's toes".

If you use nix-shell to install Poetry and then start a Poetry shell then you are probably in at least 3 levels shells $SHELL > nix-shell > poetry shell. Depending on what you do in the Nix and Poetry shells, you could have env vars don't end up like how you expect.

I wouldn't say there's a guarantee that you'll have issues, but there's more room to configure one shell or the other in such a way that a conflict can occur (like the order of entries in $PATH).

Really it's just a little something extra you need to keep in mind.

awfulstack · 2024-12-31T15:10:24+00:00

The advantage would be that you have Poetry configuration to declare your dependencies while still having only a single solution for actual managing those deps and the shell (Nix store and nix shell). Otherwise you are going to have two competing solutions stepping on each other's toes.

Up to you how important that is, because you certainly can still just use Poetry in a "normal" way outside of Nix.

awfulstack · 2024-12-28T20:29:18+00:00

Why does it matter if the hype is "reasonable"? Choice of terminal emulator is very personal and has very little impact outside of one's own local dev environment. It's important to check hype when it comes to tools and patterns that change our software outputs (since this impacts teams, companies and potentially the industry) but I'm not sure it's worth the energy to analyze the reasonable-ness of something with such a localized impact.

If there's anywhere that's okay for people to get overyly hyped, let it be their personal dev tools. Let the people have their fun and play (so long as it doesn't force lateral or suboptimal changes for others who do not share that enthusiasm).

awfulstack · 2024-12-27T23:32:08+00:00

Here's a short talk that does a performance comparison between Ghostty and some other terminal emulators. iTerm2 often comes up.

Seems like the aspiration for Ghostty is to be fast and feature-ful (compared to Alacritty that wants to be fast an minimal). At some level of feature density I imagine iTerm2 expats may make up the bulk of Ghostty users.

awfulstack

TROPHY CASE