• 10 Posts
  • 22 Comments
Joined 2 years ago
cake
Cake day: June 11th, 2023

help-circle

  • The easy part of this was that the foundation is just a big square. I picked an arbitrary size: ten 6x6 foundation blueprints on each side. The rest I just copied from inspiration images I found online. I pretty much copied an ancient building called the Ziggurat of Ur.

    I think the important thing was that I built the thing first, then started figuring out what to put in it. If I did it the other way around, I figured I’d get stuck in analysis paralysis. I did know I generally wanted to build tier 9 parts in it, so I did make sure one floor was tall enough for particle accelerators, but that’s all i planned in advance.









  • “Spam trap” and “spam honeypot” are exactly the keywords to search for. I found a bunch of info about some services you can use to set them up. I’d recommend adding “-avoid” to your search filters because every email marketer has their own article titled “About Spam Traps and How to Avoid Them” which just pollutes search results if you’re actually looking to set up your own.







  • Learning new programming languages is an awesome way to expand your programming brain. If you want to stay in the same scientific computation niche, you can check out Julia or Mathematica. If you’re just looking to broaden your horizons, the world is your oyster. For me, learning Clojure really cooked my noodle but made me a much better programmer since it taught me functional programming.

    Also, just read other peoples code! You can learn the conventions that way. Though for you it would best to find other products within your niche, because I’m not sure if general web dev code would be super helpful.

    There are techniques that are broader than any single language’s conventions, and I think learning those are how you can improve. That’s hard to teach, though, and it comes from experience with a few different languages, in my opinion.

    And honestly, I can totally respect the “conventions be damned” attitude, because at the end of the day, you’re trying to make something that works, and if nobody else is reading that code, you’ve made the right trade-off.




  • This person thinks Tailwind is just a grift to make money, prioritizes separations of concerns over all else (I contend they have SoC brain-worms, but I don’t want to get too spicy), and ignores all the actual arguments people use for Tailwind, like how it’s specifically built to suit component frameworks over someone raw-dogging that HTML and CSS. Their argument boils down to “get good” which is the argument that folks use when they’ve never been on a team and have never had to make actual trade-offs.






  • I was using Fedora for about a year and it was great. Nice and stable, almost everything worked out of the box. Then I goofed up an update and had to install something new, and I chose Arch. Arch is working mostly fine, of course I had to learn a thing or two about how some subsystems worked but the Arch wiki is a wonderful resource. We’ll see how long this install lasts, it’s been smooth sailing for about a month now.