Huh? Every IDE has had this feature for decades. Eclipse, all of JetBrains products, even NetBeans. This is like the most basic feature provided by IDEs.
Also with the development of first party language servers it’s relatively easy for new IDEs to integrate.
Or don’t support all the features
Yeah but the compilers weren’t that good at optimization back then.
Hmm… theoretically this is more efficient, however in practice you may end up with a dirty cache… I guess that’s fine if you don’t mind corruption of your coworkers.
Big companies do this all the time. Giant monorepos with good testing and reliability systems manage it. As an example: https://abseil.io/resources/swe-book/html/ch22.html
Is this an event for the next version of the Apple Vision Pro?
Some of us have PTSD from losing work back in the day. Now it’s just habit.
Aren’t brackets hard to type in Swiss layout? Most of my Swiss coworkers switch to US.
It’s very rare in the industry for you to start something and have the flexibility to pick the language. You’re much more likely to be working on an existing system or expected to work with whatever the company uses.
That said, there’s plenty of opportunity to make your own decisions. Having to follow arbitrary style rules is hardly a consideration (actually you’ll find it’s hard enough just to have consistent arbitrary rules within a company).
There may also be opportunities for you to change these rules, but it’s also wise to pick your battles.
I’m mostly talking about when you need to use JSDoc format which are usually for interfaces, so it’s usually just a chore for humans.
Probably harder to get good comments inside code, but it might still be possible.
Why wouldn’t it be able to? It can link similar code structure to data in its training set. Maybe the ones that aren’t at that level but it’s hardly a stretch to make these inferences. Most of the code you write is hardly novel.
To my knowledge that just formats existing comments. With LLMs you could probably do 95% of the actual commenting.
Your code should generally be self documenting: Have variable and method names that make sense.
Use comments when you need to explain something that might not be obvious to someone reading the code.
Also have documentation for your APIs: The interfaces between your components.
I always thought engineering is cool but time consuming. Programming was picked up along the way and now the money is too good to do anything else. Wish I could work on devices again.
That just sounds to me like he hasn’t worked on large code bases with multiple teams. No way it would be considered acceptable once you’re interesting with enough other people.
Interesting. I wonder if there are videos that increase the chance of creating infinite automata?
I feel like the subtext the post doesn’t say explicitly is that most management structure are not setup this way and thus software projects end up with a non-optimal design.
There’s probably one computer at most per employee, but each employee already has a non Windows cell phone. Most servers run Linux. Then there’s Linux in a bunch of small devices as well. Windows is a small part of that pie and only getting smaller.
Back in my day the saying was: The odds are good but the goods are odd!
I mean that just means you didn’t hack them well enough.