Re:Interviews in the Age of AI: Ditch Leetcode – Try Code Re...
by shortrounddev2 on Tuesday October 17, 2023 @08:56AM
(#37914207)
In my experience the biggest bottlenecks are in the network. Most optimizations are also very very low hanging fruit because the original code was written by a moron
Re:Interviews in the Age of AI: Ditch Leetcode – Try Code Re...
by Dudester230602 on Tuesday October 17, 2023 @09:17AM
(#37914533)
Also, using scripting languages and misusing browser engines unironically yet expecting performance...
Re:Interviews in the Age of AI: Ditch Leetcode – Try Code Re...
by shortrounddev2 on Tuesday October 17, 2023 @10:01AM
(#37915179)
Using electron isn't a performance decision, it's a labor one. It's easier to write a website once and then just export to electron than it is to rewrite your application in QT or XAML or another native desktop framework and have to hire C++ or C# developers
Re:Interviews in the Age of AI: Ditch Leetcode – Try Code Re...
by wg0 on Tuesday October 17, 2023 @02:08PM
(#37919138)
If Browsers can do Figma and VS code, they're already a far capable and approachable platform at least for most desktop applications than Qt especially for anything that has some data entry such as ERPs etc.
And it's free. Qt is not.
Re:Interviews in the Age of AI: Ditch Leetcode – Try Code Re...
by wg0 on Tuesday October 17, 2023 @02:04PM
(#37919070)
I'd estimate that 98% of companies are just receive-deserilze-validate-transform-store a.k a CRUD shops though some might have borken it down into distributed chunks (Micro Services) without any of the distributed tooling or mindset and awareness in place.
So... That's less likely where you'll need your dynamic programming or palindromes in constant time or space.
Re:Interviews in the Age of AI: Ditch Leetcode – Try Code Re...
by Tainnor on Tuesday October 17, 2023 @03:00PM
(#37919958)
> There are definitely different types of programming jobs
That's what most people on HN forget. The programming world is huge. Even more so, if you include all the stuff we wouldn't traditionally include, such as people using code to optimise business or production processes.
It's always best to assume that you don't know what "most software jobs" are like, because you're very unlikely to have seen more than a tiny slice of it.
There are definitely different types of programming jobs, but for some contrast: I have never had a job where runtime complexity did not come up as a significant factor somewhat frequently.
It really comes down to what you’re doing, but at a certain scale or size of problem you really do need to know about algorithms, data structures, and runtime complexity to avoid having your runtime explode, server costs become untenable, opening the door to extremely long running requests and other problems.