Damjan Lulakov

Self-hosted project management tool for developers github.com/usekaneo/kaneo

Finishing Alexandrescu’s Modern C++ Design and realizing you have to write React components at work tomorrow

@taylorotwell Kaneo ➡️ Linear ➡️ Jira

Jira ➡️ Linear Mailgun ➡️ Resend 1Password ➡️ ?

@jetbrains I think you need to fix the annoying autocomplete that comes out of the box with all of your products.

🤝JetBrains and Zed are joining forces to advance the Agent Client Protocol (ACP) – an open standard that lets any compatible AI coding agent work inside any editor. 🔗 Read more: jb.gg/c9mdxr

Yeah, not a big deal, but after using neovim for 4+ years, finally added the ts/js debugger.

@jetbrains Fix your annoying autocomplete on your products

01001000 01100001 01110000 01110000 01111001 00100000 01010000 01110010 01101111 01100111 01110010 01100001 01101101 01101101 01100101 01110010 00100111 01110011 00100000 01000100 01100001 01111001 00100000 01100110 01110010 01101111 01101101 00100000 01001010 01100101 01110100 01000010 01110010 01100001 01101001 01101110 01110011 00100001 🎉

I read this article about software development, which I knew about because I saw Prime reacting to it: notashelf.dev/posts/curse-of… For the most part I think it is fine: a relatively young programmer is doing the healthy work of introspecting on what he should really be doing. But there's one part of the article that I think is a deep mistake, and the author doesn't know it's so wrong because he has never experienced the alternative: "Software doesn’t stay solved. Every solution you write starts to rot the moment it exists. Not now, not later, but eventually. Libraries deprecate. APIs change. Performance regressions creep in. Your once-perfect tool breaks silently because libfoo.so is now libfoo.so.2. 2 I have had scripts silently fail because a website changed its HTML layout. I have had configuration formats break because of upstream version bumps. I have had Docker containers die because Alpine Linux rotated a mirror URL. In each case, the immediate emotional response was not just inconvenience but something that moreso resembles guilt." Yes, this is true in much of the programming world. But there is another world in which people build things that last much longer. I have done it many times. I shipped a binary for this game Braid in 2009 that you can still download and play on Steam 16 years later. If you are pretty young (like 35), you can run binaries on Windows that were compiled before you were even born, which is amazing given how hard they have been trying to f up Windows lately. On an emulator like MAME, you can play arcade games programmed in 1979. If today's software "technology" is so much better, why does it fall apart like tissue paper? The author is not wrong about the cited decay. But this decay is not inherent to the practice of software. It's due to choices made, usually foolishly, by the people designing the systems being interacted with. And, it's due to a lack of knowing better, non-exposure to the sector of programmers who are very concerned with their code lasting a long time, actually. The way you make code last a long time is you minimize dependencies that are likely to change and, to the extent you must take such dependencies, you minimize the contact surface between your program and those dependencies. The actual algorithms you program, the actual functioning machinery you build, is a mathematical object defined by the semantics of your programming language, and mathematical objects are eternal, they will last far longer than your human life. The goal then is to avoid introducing decay into the system. You must build an oasis of peace that is insulated from this constant bombardment of horrible decisions, and only hesitantly interface into the outside world. This means, for example: If you are shipping on iOS, you only reluctantly use any functions iOS gives you, because when you use them, Tim Apple will come along and break your program next year for arbitrary pointless reasons, because Tim Apple does not respect you or anyone you know. This means a program cannot last forever on iOS, because Tim Apple likes breaking your things and watching you submissively clean them up. But the core of your program, which could be 95% of the code, is fine, and you can deploy it elsewhere. This means you have to insulate from Linux userspace, because of all the jackass decision making that introduces constant incompatibilities while somehow never making the system better. Using a library dependency to do font rendering or sparse matrix math? That dependency gets checked into your source tree, a copy of exactly the version you use. Ten years later you can pull down that source and recompile, and it works, because your program is a mathematical object. If you want to upgrade to something newer that has bug fixes and so forth, you are free to do so, but you are also free not to do so, and your program still works. (And how many of these bug fixes do you really need? Your program worked correctly when you shipped it to the greatest extent you could measure, because you are a skillful software engineer who wants to ship things of a high quality). Everyone who got into programming for the joy of it knows, at some level, that the magic of programs is that they represent complexity that is replicable over time (and thus they exist outside of time). But the trashy programmer culture of the past 20 years stopped aspiring to this, and now has forgotten it is even possible. And so long as people have forgotten, decisions will continue to be made that make the problem worse. There are programmers who only write glue code, and who think that's what programming is; to these people what I have written above will not make sense. But the good news for that contingent is, they can always just stop writing glue code and start doing something else! If today's software "technology" is so good, why do you think it needs so much glue? Maybe there is a stylistic problem. So if you are looking for what to do in the world of software that can represent a lasting contribution, maybe this is food for thought. @NotAShelf @ThePrimeagen

I'm happy to say, Kaneo is in a stable and usable version and even though here I've been talking about it a lot. Officially for the rest of the world, Kaneo is released! github.com/usekaneo/kaneo

@piq9117 This is fire

I present: $2k lunch

It’s so obvious there is a 3rd hidden monitor to the right. She’s not even trying to hide it.

@t3dotgg @ThePrimeagen But is @ThePrimeagen happy ?

HTMX is all fun and games until you're unemployed because of it. It happened to @ThePrimeagen, it can happen to you as well

build

so based.

@HumansNoContext Tested ?

Only men can relate

@ID_AA_Carmack But what about the motion sickness

This is a fantastic value!

Stolen

@t3dotgg Noooooo, not Fortnite

Week 1: Prime quits Rust Week 2: Prime quits Netflix Week 3: Prime quits neovim Week 4: Prime quits Fortnite

@AKIRA_19880716 hard

@SyntheVisuals pretty

8K scanned textures for free: