It's fascinating to read these comments - I believe everyone. Some are getting huge productivity gains and others very little - so perhaps we are not in the same business. I know that I've ranged over various work - all called software development and the variety of work was quite different - some I wouldn't call challenging but still needed a lot of manual labor - perhaps this is the type of work that finds easy wins from AI automation. Still other work was much more challenging but I've never really attempted to use AI in my work because it was forbidden by policy. I've used AI at home for fun projects and it has helped me with languages I've never used before but I've never come close to 90% productivity boost. Anyway, fascinating!
I agree with your observations, in my own job I cover a great deal of the aspects of all software development practices for a few clients. Probably something you'd normally have a bunch of different roles do. Not because of AI, I have been in this role since before the AI boom, this is just how agency work is sometimes.
My observation is that there is perhaps 15% of my job that has been boosted by AI by quite a lot, and the rest it hasn't touched much at all. Most of the job just isn't coding badically. The code generation aspect is a bit flawed too because to get good results I often spend more time collating requirements and engineering the prompt that I again could have just done it quicker myself.
There is a sweet spot in there where the requirements were easy to write out, and the code was simple enough but there is a lot to write, that it's nice to not have to write it myself. But even then I am finding that AI is often not successful, and if it takes three tries to get it to do the work properly then there is no productivity gain. Often enough time is lost to the failed attempts.
Usually there isn't that much code to write, but it's fairly complex and needs to be correct, which is where I find LLMs have too many failed attempts and waste time.
(I am an 18+ year "everything" developer, my experiences are from using Claude Code)
It is pretty hard work huh! I was surprised. In my case, I was doing a personal project but in the end I felt a little crispy although the result was succesful.
there's 2 AMD KMD(kernel mode drivers) in linux: amdkfd and amdgpu .. the graphics applications use the amdgpu which is not supported by amdgdb .. amdgdb also has the limitation of requiring dwarf and and mesa/amd UMDs doesn't generate that ..
His podcast with Louie Mantia in July was pretty clear with it, though it also suggests why he’s given significant criticism of the design direction, but mostly just has quips and shade thrown at Alan Dye on the blog:
> I get to ask Alan Dye about [the shadows on Apple Watch faces]. And he was like, oh, we render a shadow? And I was like, oh, you never even looked. I just instantly realised he’d never really even looked at it. Like, somebody at Apple has, but Alan Dye didn't. […] It just suddenly came to me, oh, he doesn't do the job I thought he did.
Quickly googled his website and found this from January 2021:
> [...] I’m reminded of all the UI and interaction designs and changes in iOS and MacOS that are just bad. There’s a real sense that Apple’s current HI team, under Alan Dye, is a “design is what it looks like” group, not a “design is how it works” group.
And this, from June of this year:
> Re-watching Jobs’s introduction of Aqua for the umpteenth time, I still find it enthralling. I found Alan Dye’s introduction of Liquid Glass to be soporific, if not downright horseshitty.
He has been even more critical on his podcast. This has been a repeated refrain and increasing over the years. My first reaction, when I read the news, was "Apple bloggers and podcasters will be THRILLED."
Let's all pretend he totally wasn't going out of his way to prevent burning bridges with his Apple connections but starts throwing Alan under the bus after he's gone like he was so obviously the problem at Apple.
You seem to have an axe to grind against Gruber, are immune to all evidence against your preconceived worldview, and are projecting this behavior onto the other side of the discussion.
How about this sarcastic and brutal bit, on his podcast (end of July):
"But maybe instead of firing him, they start selling pizzas out of the back of Apple stores and Alan Dye can run that and do the graphic design on the boxes. Do the menus. I think Alan Dye could kill that with his Levi's experience, right?"
That's rougher than anything he has said post-firing, in my opinion.
Assuming the other commenter is correct and the mcu is a clone of an ST product, then it's possible that the protection are fuses that destroy the pathways to the memory. They're one-time writable and cannot be undone. At my work that is how we protect our firmware with a similar ST product.
I'm not sure how it works in-silicon. Would be interesting to know how... but it's sunday afternoon
Yup. Still fighting some collision bugs, but it mostly works. I'll post it when it's complete. What I actually wanted to do is try to put fluid movement into it - something closer to Dead Cells, just for fun to see how it would change the feel of it.
reply