Kotlin is the wave of the future. I still use Java, but I’m transitioning into using Kotlin for backend services. The devs are my work have been moving the app codebase to Kotlin for a couple of years (over a million lines) and it’s pretty nice. You reduce a lot of boilerplate and the code can be a bit more dense.
MajorMUD is the only one off the top of my head.
I’d rather go back to the 90s! The good old times, when devs can lose all that commercial software source code they are developing when the hard drive crashes! And there were no backups! Sorry people who bought licenses! 😂
Narrator: this happened more than once.
Another example of this is what happened with KeePass, then KeePassX, which gave us KeePassXC. Went from single Dev to single Dev to group of devs that were serious about the ecosystem.
I agree, writing meaningless tests helps nobody and just creates extra work everyone. Unit tests should prove functionality and integration tests act as a vise. Much like you said, if a test breaks in that scenario, then you know something in another class has violated that contract. Good tests will have meaningful names and prove functionality, especially in the backend where it is especially important…
You mention (what I would consider) a bad practice of allowing merges without review. While that should be possible on personal projects with only one dev, strict review guidelines should exist so that nobody can just “push to prod”. CICD is your friend - use it so that staging and prod never break. Again, I’m used to working on systems used by scores of millions of users so I appreciate forced automated validation. Nobody likes dumb breaks on a Friday before vacation.
That does sound like a nightmare. I’m assuming you mean failed test when you say “red boy”, and that made me wonder about PR practices. I’m used to a very strict review environment and fairly quick review turnaround or requests to go over the code. I’ve heard horror stories about people not getting PRs reviewed for days or weeks or some people just plain refusing to review code. I work on microservices that are all usually less than 10,000 lines though, not something with over a million lines of legacy code.
Yep. When I was still doing QA, I saw some pretty terrible practices and tested code that barely built. Now as a software engineer, I have no QA and rely heavily on my own testing practices, namely, unit testing first, integration testing and system/e2e testing. I can’t guarantee the code is bug free and there’s parts I know that could be refactored (tech debt), but I know each piece is tested and does what I expect it to. As corny as it sounds, I’m a big fan of TDD. Unit/IT/E2E don’t replace QA in my opinion, but better set QA up to focus on the bugs that matter and not basic stuff.
😂😂 I got downvoted for that. I guess people dislike writing tests.
Am I little naive in wondering how this isn’t caught in unit, integration and E2E tests?
Edit: looks more involved than that, but it forced me to dig into how some of the components are tested. Educational.
I’d be interested to know what “not optimized” means.
Is this something you can point yacy at?
Each fediverse service is different. Matrix has it’s own webfinger configuration, as does diaspora, and mastodon. However, it looks like all ActivityPub services use the same webfinger configuration, which means that this method doesn’t work for donations trying to reference user@domain.tld for activitypub. I would presume that the first AP service you have listed in the response is going to be the account that each AP service will federate with.
Here’s a little bit about what I’m talking about:
You do it via a webfinger. But the service itself has to request a specific resource in order to route it correctly. For example, mastodon and pixelfed ask for the same resource, so both services will end up getting the same service’s account.
Hey all! We’re on some other useless for-profit, corporate social media too!
Don’t you understand? Only a for-profit, privately held (or even better, publicly traded!) company can save us!
I’ve considered this, but my branches don’t generally live longer than a week and there isn’t usually multiple engineers working on a codebase at once. Thankfully my team is smallish and the projects are either small maintenance items or greenfield. I’ll look into where we can leverage it though!
Oh gotcha! Yeah, git merge upstreamNane branchName is the right method. Just be aware that you might have a whole host of conflicts to resolve if there’s been a significant amount of time in your branch.
One thing I like doing is creating a feature branch, then branching off that for very specific feature work. Then I try to complete that feature quickly and merge that into my feature branch and keep that up to date every day with the updated branch it was forked from. That way, I’m never too far behind production changes and the merge conflicts are kept at a minimum.
You would never just merge into upstream. You need to make sure your fork is up to date and there are no code conflicts, then you create a pull request from your branch into the branch you would want to merge into. That information will probably be in the specific projects contribution document.
Yeah, I feel like there needs to be a solution to this. Thankfully, artists don’t generally have hugely enormous catalogs that would take up terabytes of space (my entire collection is less than 400GB, which is many, many times larger than any single recording artists catalog, even the Beatles).
One rub I have with limited downloads is that memory of broken CDs. I bought a mobile app that is about $200 and they limit the number of times you can request are-download before you have to buy another license and I think it’s messed up. I’ve had to store that APK on multiple flash drives, off-site, etc.
Watch out for direct injected cars, which is virtually all of them now except for electrics. Many don’t have traditional fuel injectors in the intake manifold anymore, and because of poor PCV systems, oil vapor carbonizes on the intake valves, causing problems. This is generally around the 40k-50k mile mark, potentially sooner if people don’t drive their cars on the freeway for extended periods after startup. Some newer cars have addresses this by adding supplemental fuel injectors in the intake (some audis, some Toyotas) but it’s not a widespread practice, of it will ever be.