Kris Walker

Kris Walker

@kriswalker.me

Creating the @kixx.dev web development framework | Booster for the World Wide Web | https://www.kixx.news | https://www.kriswalker.me/

202 followers468 following695 posts

Pinned

In the long run, playing it safe is more dangerous than taking risks. Playing it safe builds in the status quo to the point where it can't be overcome.

How often have you stepped away from the keyboard, only to have the solution come to you later while you were doing something unrelated (a walk, shower, commuting)? There is a pile of scientific evidence showing that our brains continue working on hard problems in the background.

When our brains are working in the background, they incorporate more past experiences and come up with more creative solutions. The secret is that the motivation needs to be intrinsic - because you care about the problem, not because you're being paid for it.

We've spent way too many brain cycles on creating low friction ways to sling slop. Time for a change.

Kixx@kixx.dev

Creating great user experiences for humans on the web should be low friction. Contributing to the slop shoveling, bloated, frustrating web should be high friction.

A world with fewer things (less software, fewer products, less production), but things which are designed well, work exceedingly well, and bring joy to their users, is a better world. There is another world, flourishing in slop now. But, we don't have to be a part of that world. It's a choice.

I'm torn on the local-first software pardigm. While having control and offline access to your data is a huge benefit, I also despise the single page JavaScript architecture and explosion of complexity when synchronizing databases. rxdb.info/articles/loc...

rxdb.infoWhy Local-First Software Is the Future and its Limitations | RxDB - JavaScript DatabaseDiscover how local-first transforms web apps, boosts offline resilience, and why instant user feedback is becoming the new normal.

I think this means JavaScript 5 is gone. The announcement made me feel nostalgic. Remember when Array map, filter, and reduce were introduced? And "use strict"; Object.create , Object.defineProperties? We didn't have const and let yet, but we knew it was coming! babeljs.io/blog/2026/06...

babeljs.ioReleasing Babel 8 today: ESM-only, drop ES5 default, and a smooth migration path · BabelToday we are releasing Babel 8. It's been 8 years since we released Babel 7. And that's not without reason.

This phase shift in engineering cultures (it's not just Meta) is going to present some exciting new opportunities. - People leave to start their own ventures - More people leave to join them - We get a sub-culture of innovation with momentum - Break the current technology consolidation phase

Gergely Orosz@gergely.pragmaticengineer.com

This headline is pretty accurate based on Meta folks I’ve been talking with Meta is successfully destroying their formerly standout engineering culture: forcefully assigning standout devs to this unit + the layoffs It makes no rational sense. Hiring from Meta never been easier!

I'm not trying to whitewash bad news. These are real people who are having their souls crushed. I know, I felt it at my last job too. And these products have turned to garbage, through no fault of the product/eng/design people who work on them. But, it does represent new opportunities.

The usefulness of LLMs for software can't be denied any longer. But, I really don't like the closed and proprietary nature of the whole thing. It feels contrary to the spirit of programming. I'm also 100% confident we're going to find a way to open source all of this ...

I don't believe we're going to let software development itself, sit within a walled garden. We have never allowed that to happen in the past. We can't let it happen this time.

Absolutely, 100%, true. I've been working in the streaming industry for 10 years, and every year end up in contract negotiations or app rejections with Roku over the collection of data.

This post is unavailable.

Spend more time living in the now.

Piccalilli@piccalil.li

'Wise people I’ve met seem unhurried. I don’t think it’s because they’re slow thinkers or actors. I think it’s because they’ve learned that important things take the time they take, no amount of urgency changes that.' Wait it out. blog.jim-nielsen.com/2026/speed-n...

There are a *lot* of software organizations laying people off and the remainders are choosing to leave and do something else. Don't take a job just because it was offered. I've made this mistake too many times in my career. Times will change, and you'll have opportunities you won't want to miss.

taylor desseyn@tdesseyn.bsky.social

questions to ask yourself before you take an offer: >is this company growing headcount or just replacing exits >when were their last layoffs >are they still hiring interns and new grads or only senior i>s your team ai adjacent or the part getting automated

It has now been 3 months since I've had to attend a meeting. I went from 100 to zero, almost overnight. I get to live in the now, this moment, each day, every day.

Portability is absolutely critical for a truly open framework. While it is true that Cloudflare and AWS Lambda are proprietary platforms, it's hard to image how else the edge compute and tiny isolated container concepts could exist.

Kixx@kixx.dev

Build your app with Kixx and deploy to: - [ ] Cloudflare - [ ] AWS Lambda - [x] Any ol' web server - [ ] Deno Deploy

Compelling idea: Create a small language model, trained on a single software development framework. Keep it extremely domain specific. This is in contrast to the scorched earth approach taken by frontier models. Cool project by @theletterf.bsky.social got me thinking passo.uno/fine-tuning-...

passo.unoFine-tuning an LLM to write docs like it's 1995In my predictions for 2030 I wrote that tech writers would be using specialized LLMs, running locally on powerful hardware. I see hints of this move to “local first” among engineering pundits, but we’...

We need to live "in the now", more often "In 1911, Frederick Winslow Taylor turned the commoditisation of the minute into a science when he published The Principles of Scientific Management - which he had assembled by standing over the shoulder of various factory workers, wielding a stopwatch"

80% of good software is deleting the thing you were proud your agents wrote yesterday.

JA Westenberg@joanwestenberg.com

Half of good writing is deleting the thing you were proud of yesterday.

Common folks. We can do better. I know we can. Also, everyone wants to blame this on AI slop, but the enshittification has been happening for a while.

Ugghhh

Kris Walker@kriswalker.me

The software eng team at LinkedIn is shipping some real garbage lately. Terrible page load times - I mean the real page load time, not the time it takes to print a <body> tag. Failed DB transactions without rollback. Race conditions while I'm using the same browser tab

The software eng team at LinkedIn is shipping some real garbage lately. Terrible page load times - I mean the real page load time, not the time it takes to print a <body> tag. Failed DB transactions without rollback. Race conditions while I'm using the same browser tab

I'm making my SVG favicon by hand today. Because there is nobody to tell me not to ;-) That's what I love about the solo builder thing. I can prioritize crazy stuff just because I think it's important.

"I can't possibly fathom how these same idiots, the morons who continued overhiring LONG into the era of low rates, who then laid off into the same "unsuspected unchanging" rates, and are now "streamlining" for the era of AI when they, at this point, clearly have ...

zero idea how business, economics, throughput, efficient or effective AI or tying their own shoes together work... I just don't get how their stock keeps going up"

Working too much leads to busy work, which then occupies all the headspace that could be used for creative thinking. Everything I've ever done which was actually valuable, came from a long walk, a vacation, a trail run, and car ride. It *never* came from a prioritized checklist.

Be accessible We all started our software journey somewhere, and now we have a responsibility to pass our craft along to new practitioners. Our community must be welcoming and the tools we build must be friendly for new developers.

Keep things minimal Single developers and small teams have the most to gain from minimal, high quality tools. Large teams, architecture astronauts, and big enterprises move slowly and use bloated tools. In contrast, developers without that mass can move faster and build higher quality software.

Why are modern web apps sending a code to my email instead of a magic link? Is there some sort of security thing I'm not aware of, or is this lazy product development?

This is one of the primary reasons I left Disney. There is so much senseless anxiety about things that really don't matter to customers, the product, or to shareholders. All of that anxiety is pushed onto managers, who can't possibly keep it all from leaking into their teams.

The latest models seem to be converging on overfitting to software developers and programming workflows. Maybe loosen the reins on them a bit in the next post training round?

Painkiller products are hard to explain to your parents. Vitamin products are easy to explain to your parents. I identify with this. And it shows the paradox of the Mom Test

I like the idea of the "zebra" company: In contrast to unicorns, zebras are black and white: Profitable and have a higher order purpose. - Sustainable growth + long-term stability - Bootstrapped and "calm" - Prioritize quality over growth