chipdart

53 ms·

631.
by chipdart 2y ago
> I quickly realized that the map had a high overhead - all those pointers in a red-black tree consume more RAM than my data! That is true if you use std::map , which should only be used if you have a strong requirement in having sorted
632.
by chipdart 2y ago
> I mean making your entire interview just algorithms is stupid, yes That's what recruiters do when they use leetcode-type problems as their first interview to filter out the bulk of their applicantions.
633.
by chipdart 2y ago
> I think you're subject to survivorship bias. I think some people have a trick, and they desperately try to upsell their trick in order to subtly overstate the importance of their skillset. It's very hard to get anyone to be h
634.
by chipdart 2y ago
> I've seen a lot of critical fuckups in my years, but I have yet to see someone fuck up everything by using a woefully unsuitable algorithm. This bears repeating. With the exception of very niche applications, such as AAA games and
635.
by chipdart 2y ago
> This is super hilarious for code paths that try and hide network hits, such that you don't see that that loop is doing a network call per iteration. True story: once I worked on a C++ project with a very ambitious junior develope
636.
by chipdart 2y ago
> But computational complexity is a separate concern from level of abstraction. It really depends. Abstractions can and often do to otherwise avoidable copies. It's pointless to argue about computational complexity of an algorithm i
637.
by chipdart 2y ago
> I continue to insist on algorithm & data structure interviews for software engineer candidates. Not every project needs them as much, but in large enough institutions, every engineer is likely to run into at least one project that
638.
by chipdart 2y ago
> If you repeatedly contact management with the same proposal (...) My point is that at most presenting a proposal is only tangentially related with a grievance that's important enough to warrant firing someone. No one gets fired fo
639.
by chipdart 2y ago
> I agree with that - but all that browsing around also requires plenty of typing and mousing around. Navigation is largely IDE-specific, and the next best thing to a de-facto standard is VI's keyboard-centric navigation gestures wh
640.
by chipdart 2y ago
> It's unclear to me what you are trying to say here. I agree, it reads as something posted by a chatbot tha glitched.
641.
by chipdart 2y ago
> Eventually they got tired of me pitching for it and fired me. I'm sorry but your anectode is simply not believable. No one gets fired for suggesting a harmless feature.
642.
by chipdart 2y ago
> From simple use, the Beelink SER5 I have seems to have better performance than my 13-year-old Macbook Pro, so I was curious about the upper bound / limits of little machines like it. Beware of Beelink. They are known to suffer fro
643.
by chipdart 2y ago
That's fine and all, but how much time does a developer actually spend writing code? The bulk of any programming task is sifting through existing code to explore and gather context for a change. Anyone can take a look at any project&#x
644.
by chipdart 2y ago
> Websites regularly break because I don't have perfect network coverage on my phone every single day. Indeed, that's true. However, the number of users that go through similar experiences are quite low and even those who do ar
645.
by chipdart 2y ago
> I think this is where AI could be helpful in explaining and inspecting large codebases, as an assist to a developer. That's a great point. Everyone lauds the benefits of chatgpt/copilot in generating new code, but I'm st
646.
by chipdart 2y ago
To be fair, not all lines of code are equal. A project with a state machine, commands, strategy patterns, etc requires an awful lot of repetitive boilerplate. A number-crunching app or a data processing pipeline packed with spaghetti busine
647.
by chipdart 2y ago
> In Australia you're just 200ms from everything most of the time. (...) > The only app that I am always impressed with is WhatsApp. It's always the first app to start working after a reconnect, the last to get any traffic t
648.
by chipdart 2y ago
> Low bandwith, high latency connections need to be part of the regular testing of software. One size does not fit all. It would be a waste of time and effort to architect (or redesign) an app just because a residual subset of potential
649.
by chipdart 2y ago
> I still think engineering for slow internet is really important, and massively under appreciated by most software developers, but ... LEO systems (like Starlink, especially StarLink) essentially solve the core problems now. I don'
650.
by chipdart 2y ago
> But what basically ended up happening was we had 2 codebases: 1 for that non-DRY version, and then 1 for everything else. The non-DRY version limped along and no one ever wanted to work on it. The ways it did things were never updated.
651.
by chipdart 2y ago
> In such case I think I'd go for an internal-DRYing + copy-on-write approach. I agree. The primary risk of presented by DRY is tight coupling code which only bears similarities at a surface level. Starting off by explicitly keeping
652.
by chipdart 2y ago
> In fact he is right. Was he, though? I mean, yeah having to push and pop a call stack does indeed require more work than not having to do that. However, compilers can and do inline and optimize out function calls. And what's the r
653.
by chipdart 2y ago
> Readability doesn't matter much when you have 10,000+ lines of code. You aren't going to read all that code (...) You got it entirely backwards. Readability becomes far more important with the size of your project. When you g
654.
by chipdart 2y ago
> S3 is absolutely "serverless" storage (...) I think this take is ridiculous and it tries to bring absurdity to a label. Storing data on a third-party computer is not "serverless". Gmail is not a serverless messaging
655.
by chipdart 2y ago
> It seems to be quite integrated with node when it comes to some react components like next, nuxt or whatever. I find Next.js to be a hot mess of a framework. Sure, it's nice to have the whole convention by configuration thing to h
656.
by chipdart 2y ago
> separating storage from compute is kind of the definition of "serverless postgres", right? Not really,unless you want "serverless" to be meaningless. Think about it for a second: would it make any sense to call S3 a
657.
by chipdart 2y ago
> I guess the term “Serverless” is pretty ambiguous, (...) I don't this is the case though. The core principle of serverless computing is that a cloud provider supplies a managed service and scales computational resources allocated
658.
by chipdart 2y ago
> It costs time whenever a coworker has toggled the wrong setting and you must debug. Why do you have team members toggling settings at random at will? If that's a real problem with your organization, you have far more pressing prob
659.
by chipdart 2y ago
> so what? So that's exactly the whole point of this discussion: turning psychiatric labels into identities. > fact according to who? According to the fact that people do self-portray and self-identify as labels in spite of not e
660.
by chipdart 2y ago
> Everything you say is pure rhetoric, (...) Do people self-assign those labels in spite of not actually having been diagnosed with any condition? Yes or no? If the answer is "no" then your post is just nonsense.

More ›