mjr00

14 ms·

241.
by mjr00 10mo ago
> It also has already taken junior jobs. Correction: it has been a convenient excuse for large tech companies to cut junior jobs after ridiculous hiring sprees during COVID/ZIRP.
242.
by mjr00 10mo ago
The only thing we don't fully understand is how the ELIZA effect[0] has been known for 60 years yet people keep falling for it. [0] https://en.wikipedia.org/wiki/ELIZA_effect
243.
by mjr00 10mo ago
> The ground truth reality is that nobody and I mean nobody understands how LLMs work. This is a really insane and untrue quote. I would, ironically, ask an LLM to explain how LLMs work. It's really not as complicated as it seems.
244.
by mjr00 10mo ago
> Are you serious? Sam Altman and a legion of Silicon Valley movers and shakers believe otherwise. How do you think they gather the billions to build those data centers. Are they right? Are you right? We don't really know, do we...
245.
by mjr00 10mo ago
But AI is still a stochastic parrot with no actual intellectual capability... who actually believes otherwise? I figured most people had played with local models enough by now to understand that it's just math underneath. It's e
246.
by mjr00 10mo ago
It's the gaming version of Galaxy Quest: a parody that is not only great when it stands by itself, but is satirical in a way that shows they are genuinely big fans of the source material. (Though perhaps unsurprisingly, Blow has only o
247.
by mjr00 10mo ago
> So I think that a lot of juniors WILL get replaced by AI not because they are junior necessarily but because a lot of them won't be able to add great value compared to a default AI and companies care about getting the best value f
248.
by mjr00 10mo ago
I went to university 2005-2008 and I was advised by many people at the time to not go into computer science. The reasoning was that outsourced software developers in low-cost regions like India and SEA would destroy salaries, and software
249.
by mjr00 10mo ago
> So the simpler problem is that your product now becomes merely a tool call for AI agents. That's what users want. This is a big assumption, and not one I've seen in product testing. Open-ended human language is not a good i
250.
by mjr00 10mo ago
> This shouldnt be the goal. The goal should be to build an AI that can tell you what is done and what needs to be done i.e. replace jira with natural interactions. An AI that can "see" and "understand" your project.
251.
by mjr00 10mo ago
> AI-generated code still requires software engineers to build, test, debug, deploy, ensure security, monitor, be on-call, handle incidents, and so on. That's very expensive. It is much cheaper to pay a small monthly fee to a SaaS c
252.
by mjr00 10mo ago
I agree an HTTP call for every rounding operation would be awful. I would question service boundaries in this case though. This is very domain-specific, but there's likely only a small subset of your system that cares about payments, c
253.
by mjr00 10mo ago
> It’s easy to say things like this but also incredibly difficult to know if you’ll introduce subtle bugs or incompatibilities between services. You are right: it is difficult. It is harder than building a monolith. No argument there
254.
by mjr00 10mo ago
The opposite situation of needing to upgrade your entire company's codebase all at once is much more painful. With services you can upgrade runtimes on an as-needed basis. In monoliths, runtime upgrades were massive projects that
255.
by mjr00 10mo ago
> There is no one size fits all. Totally agree. For what it's worth, based on the limited information in the article, I actually do think it was the right decision to pull all of the per-destination services back into one. The share
256.
by mjr00 10mo ago
> The only way errors or issues never happened with any of the teams you worked with is if the services they were building NEVER needed to make a breaking change to the communication channel, or they never needed to communicate. Neither
257.
by mjr00 10mo ago
> If you're using protobufs, for instance, and you share the interfaces in a repo. Updating Service A's interface(s) necessitates all services dependent on communicating with it to be updated as well (whether you utilize those
258.
by mjr00 10mo ago
> If you communicate with one another you are serializing and deserializing a shared type. Yes, this is absolutely correct. The objects you send over the wire are part of an API which forms a contract the server implementing the API is e
259.
by mjr00 10mo ago
You presume very incorrectly to say the least. The npm supply chain attacks were only an issue if you don't use lock files. In fact they were a great example of why you shouldn't blindly upgrade to the latest packages when they
260.
by mjr00 10mo ago
While you're right, I can only think of twice in my career where there was a "code red all services must update now", which were log4shell and spectre/meltdown (which were a bit different anyway). I just don't think
261.
by mjr00 10mo ago
> It's likely there's a single source of truth for where you pull libraries or shared resources from, when team A wants to update the pointer to library-latest to 2.0 but the current reference of library-latest is still 1.0, ev
262.
by mjr00 10mo ago
> Once the code for all destinations lived in a single repo, they could be merged into a single service. With every destination living in one service, our developer productivity substantially improved. We no longer had to deploy 140+ ser
263.
by mjr00 10mo ago
Sure but I've worked for other places too, not just AWS. Including small startups and mid-sized companies. All of them had bad juniors--and bad seniors--who people quickly learned could not be trusted with anything and were either fire
264.
by mjr00 10mo ago
> The impact is that now, if you want to modify the project in some way, you will need to learn Go. That's tautologically true, yes, but your claim was > Either you know the problem domain and can argue about which solution is be
265.
by mjr00 10mo ago
> Such questions may be decided by personal preferences, but their impact can easily be demonstrated. I really don't think this is true. What was the demonstrated impact of writing Terraform in Go rather than Rust? Would writing Ter
266.
by mjr00 10mo ago
I have never worked with junior devs as incompetent as you describe, having worked at AWS, Splunk/Cisco, among others. At AWS even interns essentially got assigned a full project for their term and were just told to go build it. Does y
267.
by mjr00 10mo ago
> There's a reason the field is called Software Engineering and not Software Art. Words like "feels" does not belongs. Software development is nowhere near advanced enough for this to be true. Even basic questions like &qu
268.
by mjr00 10mo ago
> That's why you treat it like a junior dev. You do the fun stuff of supervising the product, overseeing design and implementation, breaking up the work, and reviewing the outputs. It does the boring stuff of actually writing the co
269.
by mjr00 10mo ago
> It really comes mostly down to being able to concisely and eloquently define what you want done. We had a method for this before LLMs; it was called "Haskell".
270.
by mjr00 10mo ago
Since when is a 4000 line of code project "advanced software"? That's about the scope of a sophomore year university CompSci project, something where there's already a broad consensus AI does quite well.

More ›