• 3 Posts
  • 3.93K Comments
Joined 3 years ago
cake
Cake day: June 15th, 2023

help-circle


  • As a long time tech user within about 5 years of retirement, I don’t quite agree with this for a couple of reasons. Tech is fine if its tech that serves me. I’m certainly not going to be doing JIRA updates in retirement, but I’ll absolutely use a web browser, word processor, and probably a coding environment for my own personal projects. Retrocomputing is much more appealing to me too.

    Also, I think most folks in IT have no idea how hard farming actually is, both mental and physically. Farming is really hard work, and having to manage some of the same annoying things we deal with in IT such as following complicated regulations, dealing with asinine people in power over you, and delivery dates.


  • But inexperienced coders will start to use LLMs a lot earlier than the experienced ones do now.

    And unlike you that can pick out a bad method or approach just by looking at the LLM output where you correct it, the inexperienced coder will send the bad code right into git if they can get it to pass a unit test.

    I get your point, but I guess the learning patterns for junior devs will just be totally different while the industry stays open for talent.

    I have no idea what the learning path is going to look like for them. Besides personal hobby projects to get experience, I don’t know who will give them a job when what they produce from their first efforts will be the “bad coder” output that gets replaced by an LLM and a senior dev.

    At least I hope it will and it will not only downsize to 50% of the human workforce.

    I’ve thought about this many times, and I’m just not seeing a path for juniors. Given this new perspective, I’m interested to hear if you can envision something different than I can. I’m honestly looking for alternate views here, I’ve got nothing.


  • It won’t replace good coders but it will replace bad ones because the good ones will be more efficient

    Here’s where we just start touching on the second order problem. Nobody starts as a good coder. We start making horrible code because we don’t know very much, and though years of making mistakes we (hopefully) improve, and become good coders.

    So if AI “replaces bad ones” we’ve effectively ended the pipeline for new coders to enter the workforce. This will be fine for awhile as we have two to three generations of coders that grew up (and became good coders) prior to AI. However, that most recent generation that was pre-AI is that last one. The gate is closed. The ladder pulled up. There won’t be any more young “bad ones” that grow up into good ones. Then the “good ones” will start to die off or retire.

    Carried to its logical conclusion, assuming nothing else changes, then there aren’t any good ones, nor will there every be again.




  • When the solution to the problems are ‘low prices sell more product’ and literally every company seems to be ignoring that

    Its not that simple. Selling more product at a lower price may not result in higher profits. These companies generally don’t care about sales as much as they do profits. Selling 10x the amount of product, but at break-even or a loss would be worse to the company than it is now with their declining sales. PepsiCo’s problem as I see it, is PepsiCo makes only a few products (some of their minor food brands) that would actually be a necessary purchase to live. Everything else they make is a luxury that people can skip if they can’t afford it.

    Everyone is getting squeezed with rising costs in housing, transportation, actual food, and medical care costs that can’t be skipped, so it is PepsiCo products (and brands like them) are the first things we cut out.




  • The good news is that is super easy to remedy.

    I have to learn the basics of stir-fry first! :) I’m a pretty basic cook, but haven’t really tried my hand at stir-fry.

    I really appreciate you sharing your knowledge on the wok cooking though, and I didn’t know about the specifics behind wok hei, though I always love that flavor from restaurants.

    However, sautéed green beans in cast iron on an induction stove is one of my go-to dishes at home. What I make is NOT 四季荳! I have to go to a restaurant for that lovely dish! There was another thread here on Lemmy we were talking about induction cooking and I had taken some picture that last time I made my green beans. You’re absolutely right on my overcrowding:

    And after looking up your comment about wok hei temperatures starting at about 260°C and going as high as 371°C, you’re also absolutely right my regular methods are nowhere near that (but until your post I didn’t know about wok hei specifics). I used a FLIR camera when I was in middle of cooking and you can see I was only at about 150°C. This was the induction element set at 6 or 7 I think:



  • Oh, there’s even more jank in this thing than the reboot workaround described above!

    I have 3 windows displaying different metrics on this display powered by the RPi. Because of the animation of each metric rendered on the display, higher value metrics will consume more CPU. Since each is a separate process, the animation in the displays would be different for each window by without any modifications. So to make each of the 3 display’s animations operate at the same relative speed, I do a calculation of how the number of objects being displayed for the metric, then add an amount of invisible (well, black on black) objects to each window so to equal a fixed amount of the animation speed I want resulting in each window having the exact same number of objects and the animations move at the same speed.

    This works surprisingly well. The only time I have to monkey with the fixed value is if I’m using it on faster or slower Raspberry Pis. For example, I’ll have a lower number of final fixed objects for an RPi 3 rather than a higher number of fixed final objects for a faster RPi 4.



  • My RPi uptime on one project will never exceed 4 hours.

    I’ve got a cron job set to reboot my Raspberry Pi every 4 hours because I wrote a crappy Python app that continuously creates objects during operation that I would have to recreate, but I can’t delete the originals, or rather, I can delete the original parent but the child survives and keeps its memory allocation. So a full reboot with autolaunch of the application on boot is my ugly janky workaround. Its a cosmetic application, nothing critical. Its just a colorful display of data metrics.

    I can hear the horror and gnashing of teeth of real developers as they read this.


  • Increasing fossil fuel - Heritage warns that the U.S. is on the verge of an electricity shortage, arguing that cutting reliance on renewable energy — and expanding oil and natural gas — is the only way to avoid a crisis.

    How are they able to say this with a straight face. “Were on the verge of a electricity shortage. We believe we should cut out a huge source of electricity to solve the shortage”.

    That’s just whackadoodle, and so is anyone that genuinely thinks this is true.