5 ms·
I was hired as the engineering lead earlier this year at a company. It was packed full of “senior” engineers who wrote nested loops, each screen was a monolith
by edgyquant 4y ago
I was hired as the engineering lead earlier this year at a company. It was packed full of “senior” engineers who wrote nested loops, each screen was a monolithic program with no abstractions etc. as I let them go we hired two more (we have a consultant that hired me and has been interviewing them) who were the exact same. Senior engineer, 15 years experience, etc.
Yes all of them appear to work a couple hours of day and I’d wager they get 3-4 jobs and work a few hours a day on each
- sicp-enjoyer 4y ago> who wrote nested loops What is this supposed to be the connotation here?
- SauciestGNU 4y agoThis suggests runtime complexity will be O(n^2), which is rarely an optimal solution to a problem.
- comex 4y agoPerhaps, but “nested loops” by itself is an odd way to describe that.
- jackblemming 4y agoUnless they verify the source code of every library they use and verify the entire call stack; it probably has a nested for loop somewhere. Good thing computers are fast!
- silvertaza 4y agoDepending on n, oftentimes nested loops are more readable and maintainable than the optimal solution. Of course too many levels of nesting is inherently a code smell that indicates other issues.
- strikelaserclaw 4y agothat says nothing if you don't know the size of the input and the problem at hand. Sometimes the best you can do is N^2.
- sicp-enjoyer 4y agoSome common cases (that wouldn't be considered algorithms) are: - working with grids (rows and columns) - iterating over nested data structures (eg. all people in a group).
- edgyquant 4y agoThat there’s almost always a more optimal solution than a triple nested loop in a useEffect. Any senior level engineer should be architecting said optimal solutions