7
Kai Lentit: Interview with Senior JS Developer 2024 (video)
(www.youtube.com)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 20 Apr 2024
7 points (100.0% liked)
FreeAssembly
75 readers
1 users here now
this is FreeAssembly, a non-toxic design, programming, and art collective. post your share-alike (CC SA, GPL, BSD, or similar) projects here! collaboration is welcome, and mutual education is too.
in brief, this community is the awful.systems answer to Hacker News. read this article for a solid summary of why having a less toxic collaborative community is important from a technical standpoint in addition to a social one.
some posting guidelines apply in addition to the typical awful.systems stuff:
- all types of passion projects and contributions are welcome, including and especially those that aren't programming or engineering in nature
- this is an explicitly noncommercial, share-alike space
- don't force yourself to do work you don't enjoy, or demand it of others
(logo credit, with modifications by @dgerard@awful.systems)
founded 8 months ago
MODERATORS
@dgerard One of the most maddening things about this video is realizing just how many modern apps are being developed with software that hasn't even reached major version 1.
Everyone is cursed with pending to use semver, or never feeling like the thing they’ve bodged together is “ready”, or are overcome with shame at how unfixably awful their creation is, and probably all three.
1.0.0 releases are meaningless now. That’s why we have zerover: https://0ver.org/
@rook "Low in the stack, low in the version. That's the HashiCorp way." 💀💀💀
to be fair, a version starting with 0 is almost certainly fair warning
Philthy doesn’t have its own versioning scheme yet, but I’m considering starting us at v1.0.0 just so we’ll never occupy the same versioning range as Lemmy or any of its dependencies
if ever there was software warranting a 0.x, it's Lemmy
as a compatible fork it might be useful to track version numbers? i guess it depends how much tracking you wanna do really
or just go to date-based releases
date-based might be prudent for what I’d like to do — essentially because we’re running this stuff in prod, I don’t want us to go in with the expectation that what we’re writing is half-working pre-beta software (though that does closely match the current reality)