acedTrex

11 ms·

301.
by acedTrex 1y ago
On any project ive ever worked on 156 -> 250 is a rounding error lol. Thats not even enough to both thinking about.
302.
by acedTrex 1y ago
Day ends in Y
303.
by acedTrex 1y ago
This is satire right? It has to be
304.
by acedTrex 1y ago
"Which is obviously increasing" With the primary advancements over the past two years being Chain Of Thought which absolutely obliterates token counts in what world would the "per token" value of a model be going up...
305.
by acedTrex 1y ago
I think its moreso their siri strategy is lacking. The personal assistant on IPhone game is what everyone is talking about.
306.
by acedTrex 1y ago
I try to use claude code a lot, I keep getting very frustrated with how slow it is and how it always does things wrong. It does not feel like its saving my any mental energy on most tasks. I do gravitate towards it for some things. But then
307.
by acedTrex 1y ago
The constructor can not do it because the constructor does not have all the data. This is lazy evaluation.
308.
by acedTrex 1y ago
What you dont like public class Repository<TEntity> : IRepository<TEntity> where TEntity : class { public async Task Add(TEntity entity) { _context.Add(entity); await _context.SaveChangesAsy
309.
by acedTrex 1y ago
I don't agree with the builder pattern. For basic objects yes its a bit silly. But the ACTUAL value of the builder pattern is when you want to variadically construct an object. Create the base object, then loop or otherwise control flo
310.
by acedTrex 1y ago
I hate this future
311.
by acedTrex 1y ago
PROLONGED outages are a failure point that more often than not, require organizational dysfunction to happen.
312.
by acedTrex 1y ago
An outage of this magnitude is almost ALWAYS the direct and immediate fault of senior leaderships priorities and focus. Pushing too hard in some areas, not listening to engineers on needed maintenance tasks etc.
313.
by acedTrex 1y ago
oh no, anyway!
314.
by acedTrex 1y ago
I mean enterprise vault has some really important features that open source doesnt. That could be a good direction to throw money at.
315.
by acedTrex 1y ago
K8s and its derivatives ultimately were designed to declaratively orchestrate stateless apis/middlewares. It of course can quite competently do many other things. But it does what it was BUILT to do originally the best and the simplest
316.
by acedTrex 1y ago
I mean a basic k3s install + a barebones deployment combined with a nodeport service is about as trivial as you can get. its not THAT much more "lines of config (60-70 max)" then an nginx conf + "git clone + other stuff"
317.
by acedTrex 1y ago
Ya this kind of usecase is for sure straying into the "this is more of a pain than its worth" with regards to k8s. Esp when you can just do basic nfs mounts in nix anyways. If you are already familiar with k8s volumes and csi&#x27
318.
by acedTrex 1y ago
A lot of the conversation about "simplicity" with kubernetes ignores that there are MANY different distributions of k8s. I would argue that k3s on a vm is not too much harder to setup than a normal reverse proxy setup. And the con
319.
by acedTrex 1y ago
I think it is really the commute that makes or breaks the office. My commute is 40 mins there and if I leave after 4pm itll take me an hour 15 to an hour 30 to get home. All in bumper to bumper standstill traffic
320.
by acedTrex 1y ago
I mean obviously if you have completely checked out and no longer care then don't bother with this.
321.
by acedTrex 1y ago
This seems very obvious to literally any one that is half competent at actual engineering.
322.
by acedTrex 1y ago
This will not stop the AI companies from using it in their training data.
323.
by acedTrex 1y ago
Basically the juniors just ask the LLM for an explanation of what the problem is and then fix what the LLM interprets your review to be talking about. The way that you solve this is that you pull your junior into a call and work them throug
324.
by acedTrex 1y ago
The standard competency markers we use to judge code have been hijacked. The new world is very low trust and very painful.
325.
by acedTrex 1y ago
So true, its well known that "ideas" came around at the same time as the advent of the modern internet.
326.
by acedTrex 1y ago
> That was never proof in the first place. I mean, it's not necessarily HARD proof but it has been a reliable enough way to figure out which corners to cut. You can of course say that no corners should ever be cut and while that is
327.
by acedTrex 1y ago
> Judging is considerably easier than writing something from scratch I don't agree with this at all. Writing new code is trivially easy, to do a full in depth review takes significantly more brain power. You have to fully ascertain
328.
by acedTrex 1y ago
> How would you even know? Seriously, if I use Chatgpt to generate a one-off function for a feature I'm working on that searches all classes for one that inherits a specific interface and attribute, are you saying you'd be able
329.
by acedTrex 1y ago
> Your premise is just fundamentally flawed. Before LLMs, the proof of a quality dev was in the pudding. After LLMs, the proof of a quality dev remains in the pudding. Indeed it does, however what the "proof" is has changed. In
330.
by acedTrex 1y ago
Author here: I quite like that quote. A very succinct way of saying what took me a few paragraphs. This new world of having to verify every single thing at all points is quite exhausting and frankly pretty slow.

More ›