whstl

43 ms·

931.
by whstl 1y ago
You can call it non-essential complexity. I don’t really care for the name but I care about grifters pretending it doesn’t really exist.
932.
by whstl 1y ago
Oh I agree. I don't really have a problem with agencies, the topic of them is not really related to my reply. My focus was more on the "disposable" part.
933.
by whstl 1y ago
People problems happen way before the first line of code is written, even when there's not even a single engineer in the vicinity, even when the topic is not remotely related to engineering.
934.
by whstl 1y ago
Another issue is when micromanagement gets in the way of transmitting importing information, it becomes more than a nuisance :/
935.
by whstl 1y ago
The super-advanced math that finance folks would throw at us was daunting. At this particular job I used the plus, the star (multiplication) and once I even got to use the minus. There's a legend going around that a friend of mine has
936.
by whstl 1y ago
Good point, I agree. I wonder if it's AI, the market, both, or some other cause... :/
937.
by whstl 1y ago
Anecdotal but: Fintech unicorn that has AI in its name, but still forbids usage of LLMs for coding (my previous job) --> no hiring of juniors since 2023. YC startup funded in 2024 heavily invested in AI (my current job) --> half the s
938.
by whstl 1y ago
A company I worked for got half a billion euros funding and the command from Masayoshi Son was to "hire as many developers as you can". That was before the pandemic and AI. It was predictable that some layoffs would eventually hap
939.
by whstl 1y ago
Argh. I had to explain recently that `a * x !== b * x when a !== b`*... it is infuriating hearing "but the result is the same in this other competitor" coupled with the "maybe the problem here is you're not knowledgeabl
940.
by whstl 1y ago
Keep in mind I said "with a good enough team". "People problems" are problems mainly caused by lack of design consistency, bad communication, unclear vision, micromanagement. A "people solution" would be to, in
941.
by whstl 1y ago
Yep. With a good enough team, even the technical problems are almost 100% caused by people issues.
942.
by whstl 1y ago
Definitely. Saying no is not really denying, it's negotiating.
943.
by whstl 1y ago
Yep. It's indeed like "management", where people expect to just slide into it as a reward for staying at a company for a few extra years. Also I hate that "architect" is used as a synonym of "cloud architect&qu
944.
by whstl 1y ago
I mean... I have been on the receiving end (as the one responsible for "installing it") of websites built by agencies and "disposable" is an ok description. Some of those websites don't really have to be maintained,
945.
by whstl 1y ago
> For agency work building disposable marketing sites Funny, because I did some freelancing work fixing disposable vibe-coded landing pages recently. And if there's one thing we can count on is that the biggest control-freaks will
946.
by whstl 1y ago
I've found that having users and fixing/building stuff for them can get the passion back, even if it's minor things where I don't learn anything technical. Just getting the feedback, implementing it, deploying the next d
947.
by whstl 1y ago
I have also encountered plenty of stubborn dogmatism at work, but not this type as much. People might add a redundant or dangerous library because they don’t know better but they don’t fight for it, like here.
948.
by whstl 1y ago
168,483 weekly downloads say otherwise. Plus, most professionally programmed React apps from the last 10 years were created like this. Vite only replaced CRA as the recommended tool quite recently.
949.
by whstl 1y ago
Nah. That's a good response in the surface, but people are REALLY good at archiving things that can be archived. I remember once going to a flea market and seeing some obviously pirate CDS labaled "Every Sega Genesis Game" ne
950.
by whstl 1y ago
The problem is that I work at a wheel design factory and get paid for it, unlike the hobbyists who make 95% of the wheels on Github. I'm all for reusing frameworks, standard libraries, crypto. Sure, those are things we don't want
951.
by whstl 1y ago
If it were my team complaining about "wheel reinvention" or "NIH" I would be ok, but I never saw this kind of gatekeeping at work. It's always internet strangers who are too dogmatic even though there's zero co
952.
by whstl 1y ago
The fearlessness of AI is indeed refreshing.
953.
by whstl 1y ago
If "this will be properly maintained" was the bar for dependencies, hello world React projects would have a double-digits number of dependencies instead of 1484 [1]. [1] https://news.ycombinator.com/item?id=3901900
954.
by whstl 1y ago
> don't necessarily force your crappy square wheel onto your dev team when better wheels exist I would agree about this 15 or 20 years ago, where I saw some monstrosities by people who didn't knew that frameworks or ORMs exis
955.
by whstl 1y ago
You're the one complaining about "hearing names of tasks you know nothing about" but you're also the one saying it should consist of "what have you done, what you will do". It doesn't. :) Stand ups are not
956.
by whstl 1y ago
It shouldn’t be a status report, though. This information is already in Jira or whatever. Someone running a standup meeting where people just repeat information is by definition not doing an efficient job at all.
957.
by whstl 1y ago
Good answer. To elaborate on it and provide examples. In languages that don't have expression inspection capabilities you have to replace the `(p) => p.Price < 100` part with something that is possible for the language to inspect
958.
by whstl 1y ago
With proper guidance, of course. If Seniors are too busy babysitting the AI, then no.
959.
by whstl 1y ago
That’s a great idea. I have limited experience scripting Blender, but there is a BPY API to add custom panels, so adding metadata to “entities” and simplifying the export workflow is probably feasible to the point it will be very close to a
960.
by whstl 1y ago
This is so cool and clever! Scott Bilas also documents doing something similar for Gabriel Knight 3, one of the “grandfathers” of data-driven engines and bit of an influence on ECS. Instead of excel however it was comma-separated text files

More ›