• 0 Posts
  • 326 Comments
Joined 1 year ago
cake
Cake day: July 23rd, 2023

help-circle


  • While it’s certainly true that some classes of bugs are very easy to fix (“oh shit I forgot to apply the correct style”; “I mean to use this method whoops”), many bugs that exist in later-stage games require pulling a bunch of shit apart to figure it out. They’re in the same pool of difficulty usually as performance optimizations or balancing new functionality. Getting a successful test case can be difficult even if the bug is readily apparent. Getting the regression test to pass is the subject of a plethora of literature. It can be hard and difficulty often scales with codebase. If the bug was obvious and easy, it would have been done before.

    If it was obvious and easy and wasn’t done before because of time constraints, devs can still charge more because their wages should have gone up. This whole thread OP is kinda nuts (not the commenter I’m vehemently agreeing with and expanding on).




  • If you are able to find a US govt job and can make it through the whatever period you need to be a contractor until you get hired on as a federal employee, this should cover you. I have a contact in a similar situation except cluster headaches. It’s going to pay less than private sector and you might have to learn some new skills for the right role. IIRC Softrams just landed a huge federal contract and hires warm bodies; might be a great place to start.

    I’ve got a lot of contacts on the market right now struggling to land a gig that wouldn’t have struggled a few years ago. Do you have DevOps skills? Any security qualifications? Get both. Are you working on certs? Do some. Have you hired a resume service? Do so. The last two are things I normally think are kinda bullshit but they are edges that seem to matter right now.

    As for a recruiting firm, I feel like all the good recruiters I’ve worked with would have advocated for me. That’s a total fucking crapshoot tho. I’ve worked with plenty that have shafted me. I don’t think there’s a specific firm for this problem.





  • If every request is an emergency that needs to immediately interrupt everything else, then your throughput is drastically reduced. The extra cognitive load that comes from the interrupts also affects throughput. If you constantly have to watch DMs/channels/email for work that might pull you away from your existing work, you’re not hitting a deep work state.

    Unless your role is intentionally interrupt-driven requests, it’s much better to drop items in a queue to be processed regularly. The tighter the deadlines, the more important moving from interrupt-driven to queue-driven is. The last 30+ years of workflow research coupled with neuroscience have really highlighted the efficacy of queues.



  • I can taste the fish quite well with soy sauce and wasabi. The saltiness raises specific flavor profiles and the wasabi kicks as those profiles are coming down. Don’t put your mouth feel on someone else unless it’s identical (it’s probably not).

    The more important difference is the quality of the meal. I’ll do whatever I want with low- and mid-tier meals. I don’t know about you; my dining out budget isn’t regularly hundreds of dollars a plate so it doesn’t really matter what the chef intended they can’t express it that well at that price point.



  • All of these packaging systems have plenty of tutorials. Speaking from experience, many maintainers were not developers when they started maintaining packages for distros other than the official distros. I have worked with several maintainers who do work in tech and know socially several who had no background. This could be a great place for you to start!

    You bother because FOSS is as much paying it forward as it is getting shit for free.