Maybe.
When using a random pivot, the worst case becomes exponentially more unlikely the larger the n. The O notation only cares about the complexity when n approaches infinity. So when n approaches infinity, the likelihood of O(n^2) performance approaches 0 (and the likelihood of O(n log n) approaches 1).
I think it’s fine to call it O(n log n).
The quadratic equation is the basis for most other math and physics. It’s used all the time.
The good thing about quicksort is that it’s a good demonstration of an O(n log n) algorithm, and that’s about it.
It wasn’t just this though; the tool itself lacks the intent, context, and limitations of what we’re doing. It doesn’t have other aspects of the project, influences, references, or personal experiences in the back of its mind, because it doesn’t have a mind.
This describes the fundamental problem with AI. The chatbot will forever be like that new recruit to the team. Sure, they have the skills to make some contributions, but they lack the surrounding context to fully work autonomously. They need some guidance to get to the right path.
The difference between the chatbot and the new recruit is that the chatbot won’t remember all the guidances it got. The chatbot won’t remember all the design decisions that were made. The chatbot won’t remember that time prod went down. The chatbot will forever be like the new recruit with no experience.
Full vibe development
I stopped coding for myself and started coding for the next person who’d touch my codebase.
Yeah. The worst code is the code only one person can work with. Sucks if that person is no longer working at the company.
”All features are xy problems”
”PM adds new features to the sprint faster than they’re solved”
”Each release require two weeks of testing”
”Each release introduces new bugs for customers despite the two weeks of testing”
From a maintainability point of view consistency is important. I’d rather work with an consistent but incorrect code, than correct bit inconsistent code. With a consistent code base it’s easier to do something about the incorrectness, especially if it’s consistently incorrect. It’s also easier to delegate the work.
Code is rarely correct forever. Sooner or later, requirements will change. What once was thought to be correct is no longer correct. It’s difficult to do anything about it if the code is inconsistent as well. It requires a lot of mental effort to understand the thought process behind some code.
I agree that correctness is the goal, but consistency is one of the best ways to ensure this goal.
One thing that isn’t mentioned regarding consistency is that it makes the code more searchable. When you start on a new issue you can easily find where you should do your work. You’ve maybe never seen this part of the code before, but you know how to find it.
This is impossible with a largely inconsistent code base. Anytime you start with a new issue you have to find a needle in the haystack.
They will resort to vibe debugging
I guess it can be a fun hobby project to learn Rust
That’s what we use in my company: a series of mini waterfalls
Waterfall only works if the programmer knows what the client needs. Usually it goes like:
They’re overlapping concepts, and can be used interchangeably. Sometimes a library can be all of them at the same time. In simple terms:
Not all APIs are libraries. For example, all websites have some interface to interact with them. A website is not a library.
Not all libraries are packages. A library don’t need to be distributed through a package manager.
Framework is a bit blurry where the line is drawn. I think if the library is used in such way that your entire program revolves around it, then it’s a framework. If you’re just using it a handful of times, then it’s not a framework.
React and Angular are frameworks in this regard. If you use them, then your entire programming is revolving around them. Any decision made is in regard to these frameworks.
I would say OpenGL is API, library and framework. Maybe also package depending on how it’s distributed.
Usually it’s just one character that’s wrong
Google seem to be particularly bad at this. They did the same with Tensorflow. It was kind of the de facto deep learning framework until Google decided to deprecate everything. Everyone responded by switching to Torch instead.
*Gen Z assembly
Jira is so badly performing I make Jonathan Blow signature rants about the state of software whenever I use it.
Nah, that’s too fancy. It’s all held together by some arcane Visual Basic macro someone wrote 25 years ago right before going to retirement and no one has dared to touch it ever since.
Maybe it’s all just one big .xlsm file?
&& git push --force