Azure | .NET | Godot | nibble.blog
Theres like a whole class of “Stuff you have to relearn every time you have to use it”: XPath, JMESPath, cron, ffmpeg, ImageMagick, PostScript etc… REGEX might be king of those :p
Also works for cron jobs, shell scripts, SQL queries, HTML layouts and the odd mermaid diagram
A single race condition is a tragedy. A million race conditions is eventual consistency.
It’s difficult problem to solve. Lemmy’s stack is a bit unconventional. The rust backend is not idiomatic and the ui is based off a template of an isomorphic not-quite-react framework. Its not impossible, but it will take a while for alot of programmers come onboard.
That being said, there’s more to it than writing code. Better bug reports, reproduction, updating docs and triaging/managing the issues is possibly more important than writing PRs. Don’t be discouraged!
Article is a bit dated and hard to read. The gist of the author is relatable though 15 years later: redundancies have been hella annoying, especially if they are unknown. Bad abstractions, however, create dilemmas, dead-locks and chicken-and-egg situations. And it’s impossible to create good abstractions unless you have no colleagues and no customers.
I would take some frustration over grinding to a halt any time.
Want and grit. At some point you’ll have to grit it out. You have to make it clear to your brain that you want it. Make it personal. Want it not the way you want to have a cookie after dinner, want it the way you want to breathe. Don’t even want the project, but want to prove to your brain that you are a rare capable human, able to start and finish a creative endeavour independently.
Make work time scarce and urgent. Having a child has done wonders for my creative output. I used to splurge 6 hour sessions kinda working on something…now I get maybe 40 minutes a day. An hour if I’m creative about it. But heck, does that hour get applied like nobody’s business.
Hope this helps, best of luck!