Definitely frontend (it's what I do, every day, and I enjoy it), but I have a great deal of experience (over 25 years), writing some pretty robust backend stuff. I just don't enjoy it as much.
I'm nowhere near that level of experience, although I've done both as well. I'm more backend oriented. And my experience has been the opposite. When I ask for backend code, footgun after footgun appears on my screen. With frontend code, much less of an issue, as far as I can tell. Part of me believes this is because I'm less skilled at frontend, and I don't bat an eye when the LLM plops down yet another useMemo (I've since learned that this is rarely needed). But in your case this argument can hardly be made. With 25 years I trust your ability to spot a good design on either end of the stack. So then I don't know where this discrepancy comes from. Maybe my prompting skills leave something to be desired.
I wonder if it's expertise gives you ability to see flaws and push the LLM past its acceptable point.
I haven't really used LLMs much for coding (sabbatical before LLMs got good at coding, now looking for work) but I found with chats that they are great at exploring well trodden territory but as soon as you go a little bit off the beaten path they flail horribly
They both do acceptably (but PHP better), as long as I don't push hard. The Swift that I get is ... meh, usually.
However, my PHP server, by design, is extremely conservative. It's meant to run on cheap shared hosting. I don't push the edges. The LLM seems to do a great job of respecting that, while still giving me good, modern, code.
The swift, on the other hand, has highly optimized UI (which also means that I'm not using SwiftUI). It shits the bed, when I push it.
I don't do "megascale" backends, though. My code is generally smaller-scale stuff that's designed to be deployed on a wide variety of cheap hosting, and is pretty conservative. It doesn't "push the limits."
I'm unlikely to run into many of the problems that (for example) the PornHub developers hit, several times an hour.
In that case, I benefit from folks like you, that allow me to have solutions that scale down to my level.
You guessed wrong. As far as I know, there's no such lobby, and I find your suggestion of its existence to be antisemitic. But the pro Israel lobby is quite open and public. Aipac's spending, for example, is public knowledge, and you can look it up for yourself.
I agree with the sentiment and dislike Kissinger, but that quote is always paraphrased and out of context.
The full quote makes it clear Kissinger was saying, in the context of the Vietnam War, that the US should come to the aid of their friends:
> "Word should be gotten to Nixon that if Thieu meets the same fate as Diem, the word will go out to the nations of the world that it may be dangerous to be America's enemy, but to be America's friend is fatal."
I'm well aware of its context and original meaning, and I'm very happy to twist its meaning into something Kissinger would disagree with any chance I get.
"we could find a nail for this hammer... or we could just hammer everything until we find the nail or make too much money hammering for a bit then sell in may and go away".
America won the space race? The only milestone where the US got there first was having boots on the moon. Every other milestone (first artificial satellite, first organism in space, first man in space, first woman, first spacewalk, first craft on the moon) was achieved by the soviets first. Taking the one arbitrary milestone where the US did come in first and declare it the finish line feels weird as heck.
Well, because obviously the finish line of the space race was the Moon.
Had the Soviets declared the line on the "first woman in space", now we probably would use Soviet GPS, we would use Soviet maps of planet surfaces, we would have Soviet Mars rovers, Soviet Voyager... You get the idea.
> Well, because obviously the finish line of the space race was the Moon.
So, this choice is not super obvious to me. If it was called the moon race or whatever, I'd get it. But in this case it just feels like making up rules after the fact to make sure you "win".
EDIT: I just realized you might be saying this sarcastically. I'm really bad at picking up on that sort of stuff, and apologize if that's the case.
My point is that the "space race" didn't really have a finish line, and despite early Soviet successes, the Americans ultimately took the lead. Because they sustained that momentum continuing to explore deep space, putting people on the Moon, and achieving all kinds of successes while the Soviets stalled and scrapped their programs, it's commonly understood (in the West, anyway, as Moon landing denialism is surprisingly rampant elsewhere) that the Americans won the race.
No need to apologize. In any case, I should apologize for hiding my point behind sarcasm.
It is sore loser behaviour. Combined with typical fascist totalitarian terrorist state mind washing of the population it does stick. Repeat lies enough time and people actually start believing them instead of the naked truth.
I feel like this argument always boils down to explicit vs implicit. It tastes the same as static vs dynamic typing. Personally, I fall well into the explicit camp. I like when I can know stuff about a function without having to read its body, and the bodies of the functions it calls, and the bodies of the functions they call, and so on. And so, I like when I can see from the function signature that it returns an integer, or when I can see from the function signature that it might do IO.
This comes at a cost, namely that of reading five extra characters in a function signature, and I could kind of imagine (truly!) how that gets in the way for some people. There is a cost of writing the five characters as well (and like the author mentions, in a poorly designed codebase, this may have to go down the call stack), but code is read more often than written, so in a sense this is negligible.
Like the dynamic vs static typing debate, I feel like this ultimately boils down to context and personal taste, and some amount of intelligence as well. I'm impressed by the amount of stuff the dynamic typing / non-async crowd is able to keep in their working or long term memory while coding. I don't have that kind of mental bandwidth, sadly.
Having said all that, this argument is disingenuous in that it completely ignores the fact that the async keyword tells you something useful (rather than some made up nonsense like color), and most of the argument basically boils down to "if you ignore the benefits, this syntax has no benefits", and I really don't respect that as an argument.
For a lot of architectures its also irrelevant. I use sync code and I use async code in my architecture. But more like independent subsystems. They are sync internally and only few places have connections to outside systems or IO. Those can be async.
I do understand though that it can be annoying for library authors, especially those that need to interact with the FS/Network etc.
No. The argument boils down into the fact that if you are not making something like Rust, coloring your functions for fine-grained performance issues is bad; if you are not making something like Haskell, coloring your functions for fine details of correctness is bad; if you are not doing something like a DBMS, coloring your objects for what code is reading it is bad; and so on.
I've been in the situation a couple of times where we had full control over choosing the frontend framework. Every time we chose React, the main argument was hirability and the fact that the engineers in question were most proficient in React. That is, inertia.
Secondly, when someone new asks me what web framework to learn, I tell them React. And the main reason, every time, is that this is more likely to get them a job, i.e., inertia.
We got here somehow. Clearly, React didn't get here purely on momentum, and must have done something less poorly than the other frameworks. But I think it's hard to deny that inertia plays a big role in its current popularity.
Yikes. You are correct. Honest truth, I got a few downvotes (after a few more upvotes), thought this was the cause, but you’re right. Didn’t think that it matters much, I’ll add it back. Had no idea anyone noticed. Fair enough, thanks for keeping me honest.
reply