1.There are three states of being. Not knowing, action and completion.00

2. Accept that everything is a draft. It helps to get it done.
3. There is no editing stage.
4. Pretending you know what you’re doing is almost the same as knowing what you are doing, so just 5. Accept that you know what you’re doing even if you don’t and do it.
5. Banish procrastination. If you wait more than a week to get an idea done, abandon it.
6. The point of being done is not to finish but to get other things done.
7. Once you’re done you can throw it away.
8. Laugh at perfection. It’s boring and keeps you from being done.
9. People without dirty hands are wrong. Doing something makes you right.
10. Failure counts as done. So do mistakes.
11. Destruction is a variant of done.
12. If you have an idea and publish it on the internet, that counts as a ghost of done.
13. Done is the engine of more.

There is also an illustration for it

Bad programmers worry about the code. Good programmers worry about data structures and their relationships.

git actually has a simple design, with stable and reasonably well-documented data structures. In fact, I'm a huge proponent of designing your code around the data, rather than the other way around, and I think it's one of the reasons git has been fairly successful

The actionable tip here is to start with the data. Try to reduce code complexity through stricter types on your interfaces or databases. Spend extra time thinking through the data structures ahead of time.

That's awesome for dev and UX feedback. It w. It follows the trend that the tool only exports into a human readable format and that's more than enough.
The UI or the interpretation of the JSON can be built later on.

Uxnote is an annotation bar for mockups and websites. Drop a single script to get text highlights, element pins, numbered cards, color theming, a dimmed focus mode, import/export, and email handoff. No plugin and no backend required.

It's similar to https://loomflows.com/ but minimalistic and provide full-control over the data.

Idea -> Programming -> Feedback. Repeat.

Half of those [students] who started from scratch had working designs.

IndexedDB built with 92% successful tests

I enjoyed the experience and don’t regret it, but experiments like this cheapen the efforts I’ve made over the years. It reduces the value of things. I think this is partly why so many of us have a knee-jerk reaction to reject these tools: if they work, then they’re frankly insulting.

Simon Willison predicts a webbrowser will be built by AI until 2029.

The 2026 State of the Game Industry report (SOTI)—an annual survey conducted by GDC Festival of Gaming—indicates that one in four game developers directly experienced a layoff over the past two years.

"Leadership failed to see that the COVID-era boom was not permanent

It seems companies have a tendency to be too greedy. It's a pattern I see more and more.

I use code, LEGO, words, pictures, wood, and empathy to create stuff. Let's make the world a bit more interesting.

A method applied from Programming as Theory Building from Peter Naur to solve the problem about a behavior of neovim.

"abstraction" in mathematics means to use a higher-level concept that carries fewer assumptions but covers a broader superset of cases. complexity is removed for the sake of generalizability. "abstraction" in programming means to paper over the underlying workings of a system with shorthands or conveniences. complexity is added so you can pretend it isn't there. no matter how you dress it up, when you're using a computer, you are always somewhere in the jenga pagoda

master the fundamentals, understand how they're composed into abstractions, and you can pick almost anything up as you go.

So how to master them?

What is a kata: basic programming concepts as akin to martial arts kata. To be really good, you don't need to study any particular big thing. you need to practice and understand the small things, over and over, until they're second nature.

Frameworks and librairies are domains of specialists.

The rest is content about programming:

Kata one: variables, flow control, scope, functions; memory semantics stack and heap
Kata two: indirection and recursion; memory semantics structs, arrays, enums

Paradigms: imperative and oop
Disgression two: odds and ends. OS, IDEs, VCS, programming loop with feedback and responses,

Kata three: registers, jumps, calling convention

once you are are good at programming, you will have literally hundreds of ideas of things to do but lack the time to do more than two or three at once. so enjoy it while it lasts

Yes indeed

The end: further reading

the important thing to remember is that it's not enough to be valuable. you must be legibly valuable. this trips up people who are not used to cultivating an appearance.

Upload the JSON output of the stats and visualize it

A thoughtful post about prioritizing new development in a project.

L’ar­­ticle parle de revue mais les deux points à rete­­nir pour moi c’est que l’hu­­main doit rester en maîtrise et toujours prou­­ver que le résul­­tat est le bon, sans juste faire confiance, et que le volume de code est un ennemi encore plus fort qu’a­­vant parce que l’IA est forte à géné­­rer beau­­coup de code.

(via https://n.survol.fr/n/lecture-ai-writes-code-faster-your-job-is-still-to-prove-it-works)

Why the author arrived at this situation?

• Have fun
• No competition
• I can do hard things
• Everyone has area of specialization
• learning comes by "being fucking around"
• these adives can be wrong due to the survivor biais

Places to start: the mozilla development network, Arch Wiki, Stackoverflow, and how I think when I think about programming

and a practice guide for computer as one image: https://jyn.dev/assets/it-is-only-computer.png

The website we needed

The website we needed

A good use of <picture>, sparingly creating a system to fetch the main content of the page, minification, image optimization of all formats,

The final product was lightning-fast even on the weakest data connections and most underpowered devices. Showing it off at trade shows, we found that competitive products were still displaying a loading spinner when our application was already loaded, rendered, and running.