Containers are nice, but don’t really cover things like firewalls, network configuration, identity management, and a whole host of other things, the configuration of which varies between providers.

Proton is a compatibility layer that basically tricks an application into thinking it’s running in Windows, allowing to run in Linux.

Is frequent rebasing something I should push for? A clean history is nice, but I’ve just won them over on feature branches… Is this something quick and easy that would improve our quality of life?

Realistically, in the short term, no. If neither you nor any of your team members are familiar with rebasing or rebase-based workflows, you will encounter problems that no one will know how to solve without researching. That’ll lead to frustration, and before you know it those old school teammates that don’t get git will fall back into using svn, or zip files with names like final_project_v1.2_final_final (copy)

I recommend getting familiar with rebase- and merge-based workflows on your own first, like on your own projects/private repos, and reading through the git documentation. Once you become more of an expert, you might be able to teach your teammates how to be proficient at using git, or at bare minimum, you’ll be able to help them unfuck themselves when they inevitably fuck their repos up.

Sounds like the onboarding process needs to have a step in it that says “here’s a link to a git tutorial, read this and get familiar with using git, as it’s an integral tool that you will use every single day on the job”. Bonus points for providing a sample repo that juniors can use to mess around with git, extra bonus points for including steps in the onboarding materials for the juniors to set up their own repos to play around with.

Yeah I’m definitely not a cryptography expert, but I’m more used to working with it in the “you need an authority to give relative meaning” use cases, not the “this signature came from that private key and that’s good enough” use cases. I feel like a lot of your examples rely on the “you need an authority to give relative meaning” use case though, and I can’t wrap my mind around a way to make that work in a way that that doesn’t largely negate the benefits you get from blockchain and it’s decentralization.

Sure, you could do that, but all that would prove is that a block was signed with the private key associated with the included public key. That doesn’t necessarily say anything about someone’s identity though does it? It just says they know how to generate a public/private key pair and a digital signature. Maybe I’m misunderstanding your example?

Sweet, genuinely thank you, my question came from a place of genuine curiosity and honest skepticism, so I appreciate the detail. I have a follow up question though. Most of those use cases seem like they’d require linking a specific identity to a given blockchain transaction. How does one go about doing that?

I see this kind of comment on pretty much every thread about Blockchain, and yet those commenters aren’t ever able to share a use case where Blockchain solves a problem better than the existing technology. Maybe you have one though?

On Gitlab, it’s in the sidebar, in a submenu under “Deployment”. It could maybe be pulled up a level, but I’d argue that’s more findable than on Github

My God y’all can’t just let a joke be a joke if there’s an option for you to be correct instead, LMAO

Edit: I just scrolled through all the comments and saw that the large majority of the replies here are very long, multi-paragraph comments. Y’all ok? Did this post touch a nerve with some of you? LMFAO

Well that’s because markdown is for documentation, and we all know programmers don’t know how to write documentation.

For that to work, the people doing the vibe coding would need to be experienced and skilled at writing test suites and managing strict version control practices. Which at that point, you’re not really a vibe coder, you’re an actual software engineer. So what you’re describing is just software engineering with extra steps lol

You should have asked them who to send the invoice to

LLMs can’t just run chromium unless they’re tool aware and have an agent running alongside them to facilitate tool use. I highly suspect that AI web crawlers aren’t that sophisticated.

deaths nuths

Does anyone remember the Microsoft Sidewinder X8 mouse? It had vertical thumb buttons instead of horizontal, and I loved that layout, but it’s literally the only mouse I’ve ever seen like it. But now that I know there’s open source mice out there, I might have to mess around and learn CAD so I can alter one of these mice to have vertical thumb buttons

Lol I’ve used both, FastAPI is nice too! I think my ideal situation would be FastAPI’s endpoints/routing, combined with Django’s ORM and DRF’s automagic serializers/viewsets.

IDK, I like Django/DRF

The whole point of a database is that you leave it where it is though

There’s an appropriate time and place for any methodology. There’s never an appropriate time or place for Teams or Jira.