• 1 Post
  • 512 Comments
Joined 10 months ago
cake
Cake day: January 3rd, 2024

help-circle







  • I adore Visual Studio for how it set the gold standard for code editing. VsCode is growing rapidly, but Visual Studio set an incredibly high bar.

    For anyone reading along, Visual Studio Community Edition was free and fantastic last time I tried it, and it does 99% of anything any individual developer cares about.

    The paid professional license shines for big messy enterprise stuff, but most people looking for an editor don’t need to worry about that.

    All that said, disclaimer for full honesty: my tool of choice is NeoVim - often with a splash of VSCodium.



  • I know a lot of people have Pis set up like this and surely they can’t be administering the whole thing through CLI, right?

    We are, indeed. I use a combination of SSH (for quick stuff), and Ansible for stuff I need to do repeatedly.

    How do I get a similar setup to my Synology such that I can just get a desktop interface in a browser?

    The tool you’re looking for is a ’VNC’ solution. There’s lots of them, and the best ones are free.

    You can enable VNC on your Raspberry Pi through Raspi-Config. You’ll also need a VNC client on each device you want to connect from. Fin linked one above, I think.

    And now some un- requested advice from me:

    You mention running Ubuntu on the Raspberry Pi.

    If you choose Ubuntu, I believe you will encounter many recipes online that will not work, because Ubuntu does not come with various Raspberry Pi specific tools pre-installed, such as raspi-config.

    Raspbian and Ubuntu are extremely similar (this is intentional).

    But I have found:

    • Many Raspberry Pi recipes will not work on Ubuntu, because Ubuntu does not include Pi specific software that is included in Raspbian.
    • Most Ubuntu recipes work perfectly on Raspbian.

    I think the Raspbian software can be added on top of Ubuntu, but I’ve never cared enough about the minor differences to even try.

    The Ubuntu recipes I have found that don’t work on Raspbian also don’t work on Pi hardware at all, until I compile additional tools from source code. (A Raspberry Pi uses an ARM chip, which is cool, but makes it harder install some software that doesn’t support it.)



  • I have seen decades of would-be “C++ killers” come and go. I think that in the end, it is C++ that kills C++.

    I think you’re right.

    I am, admittedly, a card carrying member of the C++ curmudgeon club. But I would gladly gravitate to a sexy new C++ subset for my projects, if one gains some momentum.

    I do a lot with goLang, right now, instead.

    But I would adore joining with a community effort to choose reasonable safe default C++ libraries for a bunch of use cases, if one gained the traction to cover my own use cases.


  • I don’t think it’s super useful for production (I prefer chef/vagrant)

    Yeah!

    Docker and OCI get abused a lot to thoughtlessly ship a copy of the developer’s laptop into production.

    Life is so much simpler after taking the time to build thoughtful correct recipes in an orchestration tool.

    Anything that makes it less painful for a dev to destroy and rebuild an environment that’s corrupt or even just a bit spooky pays for itself almost immediately.

    Exactly. The learning curve is mean, but it’s worth it quickly as soon as the first mystery bug dies in a rebuild fire.


  • This is great stuff.

    My comment from the peanut gallery today is just that there’s no law that CI/CD can’t be kept under control and run in ten seconds.

    Given the choice between a slow out of control CI/CD mess, or a shell script, I too will take the shell script every time.

    But I am living my best life today, and have a simple shell script in my CI/CD pipeline.



  • You make some great points, but I’m concerned that your preferred solutions may ignore the needs of working with peers. When I’ve worked with similar solutions before, we had a lot of on call, and it all went to the same person, regardless of who actually answered the phone.

    There’s nuance to be had in the middle ground:

    • The CI/CD pipeline should deliver releases, but shouldn’t be the only way to put them into production. People often get this wrong and have to invoke CI/CD to even do a roll back. Putting something into production without CI/CD should be possible, but it should be loud, to avoid nasty surprises, later.
    • Infrastructure as code is great. It just happens to be backwards, today. We could all go back to point and click changes, if the infrastructure had full journaling (including who made the change) of changes and full rollback capability. Ironically, I expect k8s (or a fork of it) to finally deliver this.
    • the only nice thing I have to say about K8s today is that it’s not locking myself into a proprietary cloud, or worse, VMWare. Today, K8s is towering mere centimeters above even worse solutions, all of them objectively awful. I’m not mad at anyone using any of these. We all know we want the freedom of K8s, but no one wants the bullshit interfaces it currently comes with. It will get better.

    Anyway, interesting read. Thank you. The only way the current awful state of hosting is going to improve is by having this conversation.

    I keep hearing “most people aren’t ready for K8S”. But there’s no such thing. There’s just whether K8S (or whatever replaces it) is ready for most people’s use cases.





  • What kind of government job specifically?

    Most of them. Certainly the ones that have unionized. If you know someone in the inside, they probably know if there’s a union.

    You’ll see more unions in government work because while private organizations breaking up unions is ethically questionable; governments breaking up unions is just openly totalitarian.

    If I can’t negotiate with a private employer, I might be a wage slave, but I can ask the government for help.

    If I can’t negotiate with my government job, it’s not actually a job, I’m just a slave.