Well yes it needs to be inaugurated first, which will not happen until January.

Damn great username btw 👌

It’s just less visible/explicit. It’s still bad press when it gets noticed and called out like in this thread, it’s just sneakier.

Security implications?

People working with these technologies have known this for quite awhile. It’s nice of Apple’s researchers to formalize it, but nobody is really surprised-- Least of all the companies funnelling traincars of money into the LLM furnace.

Okay but how does starting a secure shell help?

What if I’m already pretty good at Python and C? :)

How do you learn? I have some ESP32s that I’ve messed around a little bit with, and done some neat stuff…But I don’t have an electronics background at all and I often have trouble even figuring out how to power the damn things safely.

I feel like you just shout things into the void and people give you points for agreeing with you.

Lol at first I thought this was a direct criticism of the person you were replying to.

Thanks for explaining. I still think “planning” is a weird way to think about what’s supposed to happen during standup-- It seems to me that the whole purpose of working in sprints (and the rituals that that typically entails) is to plan ahead so that during the week you can execute on well-groomed, properly-scoped work. Of course when you notice something is wrong, or needs to be reconsidered, you might need to pull the brakes and realign mid-sprint, but my sense is that if you’re doing planning every day, that might mean that your work isn’t groomed well enough beforehand, or you’re not locking in important decisions during sprint planning.

But it might depend on the work, and it might depend on what you mean by “planning.” If your planning just looks like “Hey are you free to pair on issue 123 this afternoon? Okay sweet, I’ll throw a meeting in your calendar,” then yeah sure-- I wouldn’t use the word “planning” for that, but it’s not crazy to. Or maybe the work is different than my work, and actually does warrant some amount of day-level of planning that wouldn’t make sense for teams I’ve been on. I’m open to that, too.

(Btw I tried to look up this “planning planning feedback feedback cycle” thing and the only search results I got were THIS LEMMY THREAD, lol… Cool to see Lemmy show up in search results)

Err… Is your team doing planning during standup? I’ve never heard of that, from either people who are on teams that use standups, or from any of the Agile/Scrum literature that I’ve seen. In my experience, standups are typically about either a) coordinating the execution of work that has already been committed to, or b) whoops just a status meeting and everybody’s tuned out.

Well, have a nap

THEN FIRE ZE SAMSUNG & LG CEOS!

That’s super interesting. How do you get started at something like that? Or where would a newcomer start to learn more about it?

H e m p

+1 for “it’s unusably slow!”

I tried this last year with Linux Mint, and I learned that a normal USB drive just doesn’t have the read/write speed to even e.g. operate Firefox smoothly. There are different ways to address that, none of which really did the trick for me, so the best bet is to just get a drive with the fastest read/write rate possible. I’ve heard that it can run tolerably well on one of those more performant drives, but I didn’t try it myself.

Same experience with my relatives. I had some family whose Macbooks were no longer able to update (for Apple forced obsolescence reasons). They run Mint now, and have never had a single problem since I first set them up.

Well, one of them called me because they couldn’t figure out how to attach a file to an email… But that problem would have been identical on Mac OS.

Venn diagram of Lemmy users and Mary Poppins stans barely touching.

Yeah but you get a nice ramp-up period where you’re allowed to be bewildered and unproductive. In that time, you can probably pick out two or three grandiose changes (ideally with hot new technologies) to throw on the pile before that period ends, and use them as resume padding and interview stories for the next job.

Unlike the old developers, you aren’t complicit in the mess until a few years go by.

There’s a second-order thing going on though with tech debt that makes it different than just maintenance: Tech debt is when you address a problem in a way that makes future problems more difficult to address. So if the wire-and-tape fix is actually robust, easy to work around, and/or easy to reverse, then it wouldn’t be tech debt. But if it made it harder to unclog/clean the tap, or to fix the next leak, or install/remove things around it, then it would be like tech debt.

If that works, you should try it with a product that you aren’t interested in too and compare the results.