chipdart

11 ms·

91.
by chipdart 2y ago
> The assumption of stack ranking is that the good people will survive each round of purging. It's my understanding that Amazon does not do stack ranking. What they do is more insidious. They force people out in a process that consi
92.
by chipdart 2y ago
> Yeah but the people implementing it are prob more interested on you moving to VS (...) Wasn't support for submodules first added to Clang and CMake? Also, I don't think you fully grasp the scope of this change. Some projects
93.
by chipdart 2y ago
> I don't understand why educated people expect that an LLM would be able to play chess at a decent level. The blog post demonstrates that a LLM plays chess at a decent level. The blog post explains why. It addresses the issue of da
94.
by chipdart 2y ago
> Just because I included an rvalue constructor doesn't make it C++11. Actually, it does. I mean, does it compile when you pass -std=c++98? > This library was originally written in C. Doesn't matter. If it uses C++11 feature
95.
by chipdart 2y ago
> I just wrote a new server instead. I'm sorry, this makes no sense at all. Why would anyone write a new server just because a small component was taking a minute to build?
96.
by chipdart 2y ago
> Compile time is largely a "developer problem", but so is the usability of a library. Compiler time is way more than a "developer problem". It's an operational problem that ends up permeating to software archite
97.
by chipdart 2y ago
> Hey that is not true, at least last time I tried I spent considerable time trying to integrate a bare metal load balancer from a 9 stars github repo plugin because apparently exposing the port is not recommended. You sound like you tri
98.
by chipdart 2y ago
> It's not a show stopper though since everyone should have a c++11 compiler now (...) I think the point of pointing out it's C++11 is that it's not "classic C++" as it's using "modern C++" feature
99.
by chipdart 2y ago
> (...) and the rest of us have to suffer for it every time we experiment with a 1 line of code change to those files. If you feel this is an issue then why don't you move it to an independent submodule that can be compiled independ
100.
by chipdart 2y ago
> It makes it easier to turn them into the same unit of deployment. They are not the same unit of deployment. That's an impossibility. This critical mistake is at the core of this monorepo nonsense. It's a cargo cult, where peo
101.
by chipdart 2y ago
> Is that even such a bad thing? Given the choice between cutting expenses on food/drinks and firing people, (...) The whole point is that if you're already faced with the choice if cutting coffee or firing people, you will alr
102.
by chipdart 2y ago
> Let's say I agree with you and that TLS termination is not a container orchestration responsibility. It isn't. It's not a problem, either. That's my point: your comments were in the "not even wrong" field.
103.
by chipdart 2y ago
> Most people dont need rolling release, 24/7 availability, auto scaling, etc.. That's perfectly fine. That's not the reason why you are better off running your apps in Kubernetes though. You are better off running your ap
104.
by chipdart 2y ago
> Using Kubernetes where it's not needed is just that - wasting your time and making your life harder. I think this is a very ignorant and misguided take. Kubernetes is a container orchestration system, just like Docker swarm mode o
105.
by chipdart 2y ago
> The point of statistics (one of many) is to figure out how many observations we need. No, you're missing the whole point. Think about the problem about survivorship bias. Imagine you are at a M&Ms factory. You decide you want
106.
by chipdart 2y ago
> I'd say its 100% production ready. That's fine. Some people also manually launch containers individually with Docker as their production system. They'd be wasting their time and making their lives needlessly harder, thou
107.
by chipdart 2y ago
> For many people self-hosting implies a personal server; it's not really "development" but it's not "production" either. There's Docker swarm mode for that. It supports clustering too. It's nuts h
108.
by chipdart 2y ago
> This company is done. This is hard to understate the importance of this. If a company feels obligated to cut spending by cutting small expenses on consumables, such as coffee or even free fruit programs, then they are at a level of goi
109.
by chipdart 2y ago
My answer was not touching on the topic of identity. I'm referring to the relationship between cause ad effect.
110.
by chipdart 2y ago
> At what point do we conclude the lottery isn't as random as they claim if one person keeps winning. The whole thing about survivorship bias is that you make a critical failure in analysis when confusing partial observations of pos
111.
by chipdart 2y ago
It's not about interns, it's about roles. L6s are tasked with interfacing with higher-ups, such as product owners and senior managements. They coordinate with principal engineers to design and deliver critical features. They help
112.
by chipdart 2y ago
> (...) and they keep winning That's the textbook definition of survivorship bias. It's like a lottery winner boasting about his winning strategy that everyone else is just not able to learn.
113.
by chipdart 2y ago
> I would think that about 20-30% are “senior”. I think your assumption is way off. From what I've gathered, each team typically has a single L6 engineer (some have zero), and each independent organization has a single L7 engineer.
114.
by chipdart 2y ago
And by "TikTok" implies state-run propaganda campaigns.
115.
by chipdart 2y ago
> Can you show me an example of successfully doing what you claim you do? In theory technically nothing prevents me from doing that, but I use it for professional work. Do you understand what you're asking?
116.
by chipdart 2y ago
> I am unable to get these things to do anything useful. My experience is widely different than yours. I use Copilot extensively to explain aspects of codebases, generate documentation, and even fill in boilerplate code for automated tes
117.
by chipdart 2y ago
> Somehow I feel the project was held as a hostage, waiting for a ransom (which was paid eventually). This situation only happens when you hand the responsibility of managing a critical domain to a single person, and you forget about it
118.
by chipdart 2y ago
> That pretty much makes all internal APIs and code like Public APIs as a product (...) No. Different versions are not different products. They are the exact same product, provided in a way that delivers features in a way that won't
119.
by chipdart 2y ago
> To put the opposite view: Versioning could be done with individual functions in the code for example but we don't do that - we just update all the places that call it. I think you're a bit confused. There are code repositorie
120.
by chipdart 2y ago
> Bugs can and will happen, eg. when A depends on B and some developer accidentally makes a change to B that will pass B's tests but only break in A's use case. In monorepo case such bug can be noticed before the broken code hi

More ›