What is the exact definition of an IDE? JetBrain's products are as good as ever, in my opinion, but people have definitely made non-IDEs into big, hulking behemoths with tons of plugins. If anything, maybe "just an editor" is dead?
I think they mean the transition that all IDE's are making towards an agentic interface, hiding the code completely as humans will not have to interact with it since the AI will be doing a better job at everything, even auditing it.
@fastidiousprofilefollow"Beware those that would deny you access to information, for in their heart they dream themselves your master." โ Sid Meyerswrote:
Do you live there or are just visiting? I remember feeling so at home there as a kid. I never kept my French up so I don't think I could ever move there.
Visiting, for the first time. It's about a 9 hour drive from home so we've never made the trip, but so worth it. Went to Ile d'Orleans yesterday, just... so quiet and beautiful. Seems a bit of a paradise, haven't even made it up to the natl park(s) yet.
My French is coming back a little each day, made it all the way through the coffee order just now :)
@thechelsukprofilefollowCurrently in remission from ME/CFS after 3+ years. Occasional software engineering leader, app developer, blogger, zwifter, and just being online.wrote:
Added it as a company on LinkedIn so it must be 'live' now. Cheltenham-od.uk
Inspired by two projects of github:schildep I start to explore what can be expressed in Lean and make coding agents implement and prove the implementation at the same time.
I've been enjoying toast to help click through a project. I still mostly use Zed to handwrite code, but it's nice to open a pane and fire up toast from the terminal. paradise-runner.github.io/toast/
Similar with having access to so much critically acclaimed media, but they are so emotionally or intellectually draining that I find myself rewatching ol' familiars. Availability seems just one aspect, and perhaps not even the most limiting factor. Maybe most people have a "limit" on number of "lives", as in number of times you fall in love, change, get inspired, connect, etc..
code quality is about coupling.
coupling is not a technical property of the code bytes.
code acquires its meaning in contact with the cultural environment, and coupling is about meaning.
two constants with no semantic relationship are nonetheless coupled in pragmatics if they refer to the same domain concept.
if your goal is to minimise the time integral of future work, you must understand your domain: it decides which lines will need changing.
to carve up a codebase is to carve up the world.
I think you're right but executing on that idea requires a lot of care. It's similar to how functional programmers pathologically fear state; sometimes coupling/state are a necessary evil in order to keep the theory simple.
true! i might have been wiser to say: code quality is about managing coupling across the whole system. extracting a coupling sometimes requires you to introduce complexity beyond that which the extraction reduces.