HN user

stack_framer

709 karma

Husband, father, and software developer living near the beautiful Rocky Mountains of Utah.

Posts5
Comments149
View on HN

I'm building a family game server that will host web-based games on my local network (although I'm thinking about using something like Cloudflare Tunnel to make it available on the internet).

The first game I'm building is the card game Phase 10, and I'm done with phases 1-7. After that, I'd like to build Carcassonne, and maybe Jeopardy.

No, but this is a great suggestion. I imagine a flow that looks something like this:

(1) When creating the textile, you would add a step to "wait for new clipboard data."

(2) When you run the textile, and it gets to that step, a modal would appear, prompting you to copy the new thing to your clipboard.

(3) Once you've got the new thing on your clipboard, you would go back and click "Continue" on the modal from step 2.

(4) Textile would continue with the new thing on your clipboard.

Is that kind of what you were thinking?

I'm not too familiar with Espanso, but Textile is not a text expander. Textile allows you to pre-define a sequence of steps that dynamically generate the text you want, by running commands on your computer, reading your clipboard, or using hard-coded text you provide.

Here's a quick example, and one that I often use with Textile to generate a preview URL based on my current branch:

(1) Start with the output of the command `git branch --show-current` in the `~/code` directory (yielding text like `JIRA-1234/some-feature`).

(2) Replace all `/` characters with `-` (now the text is `JIRA-1234-some-feature`).

(3) Prepend `[preview](https://staging-`, which is the start of a markdown link (now the text is `[preview](https://staging-JIRA-1234-some-feature`).

(4) Append `.example.com)`, which is the end of the markdown link (now the text is `[preview](https://staging-JIRA-1234-some-feature.example.com)`).

(5) Copy the result to my clipboard.

With those steps saved in Textile, I can now click a button to run them over and over again (or use a keyboard shortcut if I assigned one). So no matter which branch I'm on, I'll always get a proper preview link without having to construct it manually myself.

I'm reading The C Programming Language, 2nd edition (the K&R book), and working through all the exercises.

It's a great book, although it's forcing me to admit that I need glasses (the print is so small)!

"...fewer than 4,000 jobs, representing less than 5 percent of our total employee base."

I cringe at this attempt to soften the numbers by saying "fewer than" and "less than" here. Conversely, and ironically, it also puts inflated numbers in your head.

"How many people will be axed at Cisco?"

"3,998 ... but at least it's fewer than 4,000!"

Location: Salt Lake City, UT

Remote: Remote/Hybrid/On-Site

Willing to relocate: To Arizona, Texas, or Florida for the right opportunity

Technologies: TypeScript, React, Next.js, Node.js, PostgreSQL, AWS

Résumé/CV: https://drive.google.com/file/d/1CUhv4zVHxUlkLidmVu19ZacPhMf...

Email: rob [dot] johansen at gmail [dot] com

I just got laid off by Pie Insurance, along with 64 other people (including staff software engineers, engineering managers, product managers, and other roles). I worked across the stack at Pie, building design systems and reusable UI components on the front end, as well as APIs and event-based systems on the back end.

Our first year on Vercel, the bill was $40,000. When our management went back to negotiate the second year, Vercel wanted $120,000! Vercel wasn't offering 3x the features, mind you, they just knew we were locked in. Our management got it down to $60,000 (still a 50% cost increase, year over year).

Our app is small beans, too. We don't even have that many users. To borrow a favorite term from DHH, Vercel are "merchants of complexity."

But they're only half the problem. Our management is the other half. They can't be bothered to grow a spine and move away from Vercel. So we'll just keep paying, and eventually some people will "be affected" by a "reduction in force."

I once had an external monitor with a maximum refresh rate of 30 Hz, and mouse movements were noticeably sluggish. It was part of a multi-monitor setup, so it was very obvious as I moved the mouse between monitors.

I'm not sure if this LG display will have the same issue, but I won't be an early adopter.

My wife and I canceled Netflix a while ago and went back to DVDs. An FYE store in our area recently had a store closing sale, so we bought three DVD players and snapped up all our favorite DVDs for a few bucks each.

No subscription, no mid-movie ads, and no worrying about this or that service losing the streaming rights to whatever.

I never actually type semicolons in my JavaScript / TypeScript. In work projects, my IDE adds them for me thanks to the linter. In personal projects, I just leave them out (I don't use a linter, so my IDE does not add them), and I've never had a problem. Not even once.

Semicolon FUD is for the birds.

I'm seeing a 404 page. I assume this is unintentional, but it's making a funny point: How could AGI possibly be imminent and we still have 404 pages?

Regardless, I agree with this article whose body eludes me: AGI is not imminent, it's hype in the extreme. It's the next fusion. It's perpetually on the horizon (pun intended), and we've wasted trillions on machines that will never reach it.

Wow, this is a new low I did not expect to see. "Just get high and you'll be able to code with an LLM." Preceded by, "I know it's terrible."

I'm wholly unwilling to relinquish my health and my morals to "AI" so I can "ship faster." What a pathetic existence that would be.

We mourn our craft 5 months ago

I find it such a strange cycle to tell AI to write some code, then tell it to fix the bugs in that code. Why didn't the AI just not include those bugs the first time it wrote the code?!

We mourn our craft 6 months ago

your world view has fixed into a certain way the world works

Yeah, it's weird. I'm fixated on not having bugs in my code. :)

We mourn our craft 6 months ago

But it is coming and you will either have to adapt or become irrelevant.

I heard it will be here in six months. I guess I don't have much time to adapt! :)

We mourn our craft 6 months ago

wait six months.

I mourn having to repeatedly hear this never-quite-true promise that an amazing future of perfect code from agentic whatevers will come to fruition, and it's still just six months away. "Oh yes, we know we said it was coming six, twelve, and eighteen months ago, but this time we pinky swear it's just six months away!"

I remember when I first got access to the internet. It was revolutionary. I wanted to be online all the time, playing games, chatting with friends, and discovering new things. It shaped my desire to study computer science and learn to develop software! I could see and experience the value of the internet immediately. It's utility was never "six months away," and I didn't have to be compelled to use it—I was eager to use it of my own volition as often as possible.

LLM coding doesn't feel revolutionary or exciting like this. It's a mandate from the top. It's my know-nothing boss telling me to "find ways to use AI so we can move faster." It's my boss's know-nothing boss conducting Culture Amp surveys about AI usage, but ignoring the feedback that 95% of Copilot's PR comments are useless noise: "The name of this unit test could be improved." It's waiting for code to be slopped onto my screen, so I can go over it with a fine-toothed comb and find all the bugs—and there are always bugs.

Here's what I hope is six months away: The death of AI hype.

I wish there was a way to straighten myself out after I drag with the mouse or use the A/D keys to move left or right. I was expecting to be able to turn left or right, and weave through the servers (or whatever they are), as opposed to drifting left/right and eventually getting stuck.