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

help-circle
  • Unless you’re an independently wealthy jackass, I’m not sure how you can attack non-FOSS software users. I am a software engineer and I get paid to write software. I write some code for fun at home too and if people use any of my projects Im delighted. But if you want bug fixes and reliability and consistent new features and updates to apis and I have to listen to your bullshit complaints about how XYZ is better, you bet your ass I’m gonna charge for that.

    It’s like a baker making bread who gives out a few loaves for free at first. You don’t get to complain if 100s of people show up demanding free bread and he starts charging them. Maybe communism is a system that demands people work for free, but elsewhere you’re entitled to whatever wage the market will bear.











  • There is definitely a huge difference after 6 months of focusing on one thing. I’ve done hot yoga off and on over about 12 years and I’d say it took 6 months of going consistently before I felt like my body adjusted and it was more enjoyable. After 2 years I didn’t feel like I was going to die and it actually became very enjoyable.

    I’ve fallen off recently because it’s easier to sit around and initially it does suck because you need to readjust. But I when I had gone 2-3x in a week, man I felt like a god. I started going in my 20s, I was high af all the time and knew I needed some exercise or I was gonna die.

    I think it takes a certain person to love lifting weights of all things. But luckily there are lots of things out there



  • Personally I try to keep my code as free of branches as possible for simplicity reasons. Branch-free code is often easier to understand and easier to predict for a human. If your program is a giant block of if statements it’s going to be harder to make changes easily and reliably. And you’re likely leaving useful reusable functionality gunked up and spread out throughout your application.

    Every piece of software actually is a data processing pipeline. You take some input, do some processing of some sort, then output something, usually along with some side effects (network requests, writing files, etc). Thinking about your software in this way can help you design better software. I rarely write code that needs to process large amounts of data, but pretty much any code can benefit from intentional simplicity and design.