I’m just a nerd girl.

  • 1 Post
  • 12 Comments
Joined 2 years ago
cake
Cake day: September 18th, 2023

help-circle
  • Can someone still developing tell me what I should use for the backend today?

    I recommend checking out Python (Django) and Ruby (Ruby on Rails) if you want nice and easy modern Web frameworks that also aren’t that weird if you have PHP experience.

    Also I can never understand GIT as a single developer. The fuck is that? I’ve tried everything to understand.

    Versioning your code with Git makes it much easier to experiment with new ideas. Cocked up a file? Pull it from the previous version. Create new branches for experiments, merge them in if they work, toss them if they don’t, or keep them around just in case, without them ever getting in your way in the “real” version.

    And if you keep the code in a server (GitHub etc), that gives you a backup location and makes it easier to work on code on multiple systems.


  • Reminds me of how in some old Unix system, /bin/true was a shell script.

    …well, if it needs to just be a program that returns 0, that’s a reasonable thing to do. An empty shell script returns 0.

    Of course, since this was an old proprietary Unix system, the shell script had a giant header comment that said this is proprietary information and if you disclose this the lawyers will come at ya like a ton of bricks. …never mind that this was a program that literally does nothing.







  • In the late 1990s/early 2000s, there was some satire article about how to get most effective Linux support. Just write an angry news/blog article about how Linux sucks because it doesn’t (insert the thing you’re having problems with here). You bet someone will immediately respond how you’re an idiot and you should (insert detailed explanation of how to fix the thing here).



  • It’s even funnier because the guy is mocking DHH. You know, the creator of Ruby on Rails. Which 37signals obviously uses.

    I know from experience that a) Rails is a very junior developer friendly framework, yet incredibly powerful, and b) all Rails apps are colossal machines with a lot of moving parts. So when the scared juniors look at the apps for the first time, the senior Rails devs are like “Eh, don’t worry about it, most of the complex stuff is happening on the background, the only way to break it if you genuinely have no idea what you’re doing and screw things up on purpose.” Which leads to point c) using AI coding with Rails codebases is usually like pulling open the side door of this gargantuan machine and dropping in a sack of wrenches in the gears.