• 0 Posts
  • 323 Comments
Joined 2 years ago
cake
Cake day: June 21st, 2023

help-circle

  • Oddly if you look into a lot of them, there were a lot of “small business owners” that aren’t beholden to a company or people connected to someone else’s wealth, or illegal under the table wealth, or other shady things. It has been a while since I looked into it, but it was a combination of personal fiscal stupid decisions, access to rich with money to burn. The tl;dr was basically: they didn’t care what they did to themselves because they thought The Orange Oompa McBurger Loompa was going to anoint them all soldiers of his magic rich person court.

    When you have a fatalist/selfish/sure-thing psychology working “outside” the system, you really don’t care if your kids have medication, and you don’t lose your health insurance because you’re taking Ivermectin from the neighborhood vet that sells it under the table.




  • So, time to stop paying federal students loans and income taxes, eh?

    Edit: student loans would be more difficult because loan default but the W4 can be adjusted so no income is deducted for Federal taxes. One would just have to be sure to put that money aside in a savings account to pay next year with no current impact in this tax year. Looks like there would have to be some quarterly payments or one would otherwise incur penalties. So it’d be a bit tricky to pull off cleanly. Maybe someone better at tax code could figure out a way to just do this quarterly.









  • It helps to be a little bit stubborn, but mostly, remind yourself it’s just software at the end of the day too. So many devs are judgy and think there is only one “good” way to solve a problem, which ends up creating a sort of tunnel vision. As soon as you let that go and just know that every problem could have any solution, especially the unexpected, you see your way through faster.

    It doesn’t matter if the way it was working is “right” or not, it was working, for reasons, so fixing it, is just teasing out those reasons. Be it from humans that may still be around, but most of the time, by feeling the code out.

    I even see the struggle externally from afar when companies I used to work at release a new feature that touches very legacy code and, time and again, the new feature is buggy AF. The new dev likely had no idea what the old dev was thinking or why, and thusly, breakage. Neither of them is right or wrong, the solution from the past likely was obscure due to constraints that no longer exist, the new solution can be done easier due to a plethora of libraries that now exist, and getting newEasy to jive with oldBespoke trips the new dev up as they unravel what looks like pure chaos.