• 0 Posts
  • 13 Comments
Joined 1 year ago
cake
Cake day: June 10th, 2023

help-circle

  • Respectfully, this is why we can’t have an actual conversation about healthcare in this country. What’s objectively a societal good? Medicine? Sure, but I’m not proposing that we stop practicing medicine. Universal access to healthcare, free at the point of delivery? Also good, and a feature of most healthcare systems in the developed world. The specific funding model where the government runs the entire healthcare system through taxation?

    I dunno, seems like it gives good, but not great, results, terrible staff morale, and a permanent state of crisis.



  • The British NHS should be replaced with a system of national insurance. I’m a staunch labour voter, but the current system is subject to endless tinkering by the party of the day, and it’s broken.

    In the UK, the NHS is one of the only institutions that attracts broad unreserved support, though, so this is about as popular as “all college athletes should be locked in churches and those churches should be burned to the ground” would be in the US.


  • When I first started programming I used a text editor, UltraEdit32. When I moved into .Net, I initially used Ultraedit and wrote all my own build files, but switched to using Visual Studio with all the bells and whistles. When I moved to Python/Node I adopted Vim, and these days I tend to use Doom Emacs.

    There’s a spectrum from visual studio or eclipse, with complex project structures, through vscode and rider which are simpler, to programmers editors like Emacs or neovim, to plain editors like nano.

    I think the most important thing is that you’re comfortable with your tools. I could crunch out a lot of code with Visual Studio and Resharper, but I use Emacs as an IDE, note taking tool, and email client . The familiarity makes me productive.

    It is super helpful to have syntax errors or warnings highlighted when working on code, and a decent editor will make it easier to navigate code - jump to the definition of a function, find the documentation for an API call etc.

    As codebases get larger, you need all the help you can get. You may also find, when you work with others, that their opinionated tooling clashes with your opinionated hand crafting.





  • Some things can go faster if you add more workers, some things can only go faster if you make the workers bigger or faster .

    If you’re tidying a garden you can get it all done more quickly, and tackle bigger gardens, by getting your friends to help. That’s horizontal scaling.

    If you need to get a parcel from your house to Burkina Faso the only way to do that more quickly is to use a bigger, faster machine. That’s vertical scaling.

    The way Lemmy is designed right now (says the op, I don’t know the detail) you can only support more users by making the server bigger and more expensive, not by using lots of smaller servers.

    Edit: note that Lemmy as a whole scales horizontally: more instances == more users, but each instance has to scale vertically.