davidfactorial

This is one of the best articles I've read in a while about the philosophy of software testing, which has felt opaque to me at times.

Nice to have this person's high level thoughts all spelled out.

Go off into the woods, literally or not. I went back to my parents house for a year and that's how long it took to overcome my burnout. Life is finally starting to feel exciting again.

I'm now exploring spirituality outside of religion for the first time. It's helped greatly with the anxiety and existential dread.

I think the Reverse Emulation was one of the most technically impressive hacks I've ever seen.

The best thing I ever did for my hands was putting ctrl to the left of the spacebar where alt usually is. I hit it with my left thumb. I never have to contort my wrists. And it works across all programs, not just vim/emacs. Capslock is still using the pinky.

I also switched to Dvorak and put backspace on Capslock, which I think also helped but might be diminishing returns. But I still really like ctrl on alt for my single best ergonomics tweak.

sure - email or tweeter me, links are in my profile

The ability to use even a small amount of arbitrary code really increases the utility for me

Congrats on the 2.0 release! Python support and the key/value store is super cool to see.

Recently used Pipedream very successfully on a freelance gig to create a search widget powered by a client-editable Airtable base that auto-feeds into an Algolia index.

I'm excited to play around with v2, have been promoting Pipedream in my little Discord community of scrappy devs. Best wishes on your continued success.

i think you may have suddenly helped me to finally grasp the true essence and nature of tdd. woah this makes so much more sense

Incidentally the few games I have actually finished were all Ludum Dare games with a very short timescale of 2-3 days.

I relate to this a lot, having also started and then not finished a lot of games like the author.

Perhaps it seems obvious to say, but I have only recently fully internalized that making games is not the same activity as playing games, and that it will take many orders of magnitude more time to polish even one gameplay feature compared to how long it will take for that gameplay feature to become stale _to me_ as the dev playtesting that feature over and over again.

I wonder if a lot of gamedevs just get tired of playing their own game and thus don't care about it anymore as a result?

Seth Godin has a book called The Dip about the slog in the middle that many creative projects have (business starting as well). I wonder if gamedev has a particularly nasty dip and that is why so few finish.

Oh my goodness this is the out loudest I have laughed at a tech thing in a long time. Cheers to you :)

I'm a large fan of Django/Python for anything CRUD-like.

It has been my go-to web framework for the better part of a decade and I continue to be impressed with it. "The web framework for perfectionists with deadlines" tagline is quite apt, as it has the highest combo of power and developer efficiency of any framework I've come across even today.

It is Python, which gives you the entirety of the Python ecosystem including all of the data science stuff and a bunch of Django-specific extras if you need them.

With the recent crop of Javascript-less tools like HTMX and AlpineJS you can do most things without any Javascript at all. Bootstrap or Tailwind both work great for CSS.

I still find the database ORM to be one of the most pleasant ways to interface with a datastore, and the migrations system usually makes database changes pretty easy. Can work with Postgres, Sqlite, mySql and a few others.

It has basically zero external dependencies besides one or two tiny ones.

I've been pleased with how easy it has been to keep Django upgraded. It feels like relatively little has changed in a backwards incompatible way compared to some of the frontend churn I've experienced.

It's widely used, and so it is relatively easy to find people who can work on a Django codebase compared to something more obscure. Django embraces convention over configuration, so if you've worked on one Django codebase you can probably work on another.

The documentation is excellent, and since it is widespread there is a huge amount of learning materials, articles, and Stackoverflow questions around.

Django has 16 years worth of work put into it and is extremely well tested. It implements a lot of the security things I have no interest in trying myself, like password hashing, sanitizing, etc.

Unless your requirements call for extreme performance needs or massively big data, Django can probably handle your workload just fine.

You can get pretty far with the base framework, and then if you need something else, consult the massive list of extras: https://awesomedjango.org/

Happy to answer any Django questions. Cheers