Having worked at two big tech companies, I’d say one was the most laid-back, stress free environment I’ve ever worked in, and the other was pretty middle of the road.
I'm all in favor of talking about drawbacks of AI coding and potential future problems. No problem. But at this point just the blanket statement that you'll never use it is not reasonable. It's the equivalent of a master car mechanic seeing a robot that can pretty reliably rebuild a transmission in a few minutes saying "I'll never use that; I'll always do it myself." Okay, sure buddy. You keep taking 8 hours to do what now takes everyone else 5 minutes. Knock yourself out.
almost everything he says is reasonable and correct though. using AI does undermine understanding, and companies hiring less juniors will be the death of them. Also juniors using AI will be the death of deep understanding if they continue. Robots fixing cars is not an apt analogy because it's a rote task. LLMs are being used for far beyond rote tasks and that's where the danger lies. People forget that most frustration and struggle are crucial, not something to remove. And people especially beginners do not have the judgement to know when struggling is appropriate.
By analogy, you can imagine a mid-century human computer shouting "I will never use computing machines to perform numerical calculations! I must perform every addition by hand!" You can even imagine a commune forming around "hand-made calculation" and trying to sell services that are certified "automation-free".
They don't? It is taught in schools in the early elementary level. I see no indication that most are failing.
I think we can agree that few of them would be economically useful due to not knowing what to program. There is no sign of competency on that front. Certainly, even the best programmer in the world could theoretically be economically useless. Programmers only become economically useful when they can bridge "what to program".
> They don't? It is taught in schools in the early elementary level. I see no indication that most are failing.
Programming in elementary schools typically involves moving a turtle around on the screen. (My mother taught 4th grade in New York for many years, and I believe her when she explained the computer instruction.)
Economically valueable programming is much more complex than is taught in many schools through freshman college. (I taught programming at the college level from 1980 till I retired in 2020.)
Because economically valuable programming has to consider what to program, not simply follow the instructions handed down by a teacher of exactly where and how to move a turtle on the screen. But nobody questions "what to program" not being hard. It was explicitly asserted in the very first comment on this topic as being hard and that has also carried in the comments that have followed.
> artificial deadlines preventing me from writing proper unit tests, or the requirement for code review from people on my team who don't even work on the same codebase as I do on a daily basis
I have never experienced this, and it sounds remarkably dysfunctional to me.
Believe me, it is very dysfunctional. As I've mentioned to your first replyer, my boss has only had developers for less than a year. This is an operations team I was assigned to in order to provide them some much needed tooling. The pressure my boss has perceived from above has led to my own significant burnout. The guy does not take days off and has always been logged into Slack on the odd hours I would need to pull up some HR form or another. I am currently off work for several months dealing with the fallout from all that.
I've tried everything I can to cope and am not sure I will be willing to return to that team once I am past my medical leave.
Beg pardon? I've been doing this for 20 years. My boss has been a boss for two years and has only had developer headcount for less than a year. This degree of pressure is unprecedented in my career.
You've missed the point. The point is that the women in question demand it. There is no shortage of women on social media ranting about how lazy or cheap men are who want to do coffee or drinks for a first date. Or especially a walk. If you suggest a walk for a first date there's a strong chance you'll never hear from her again.
So, you've saved yourself the time and expense of a shared walk and two cups of coffee. Isn't that a win? Unless you are just looking to get laid, in which case, suck it up and buy dinner, I guess.
Yes, but the point is that people are not successful on these apps because of those expectations. A lot of people have sort of let the whole online dating thing go straight to their head. And now, theyd rather die alone than be slightly uncomfortable for a few minutes.
I'm not, was just responding to the apparent frustration and finding people who want expensive dinners dates. If that's not your thing, great, there are people out there who would love a coffee and a walk or whatever. I'm one of them. A formal dinner on a first date sounds awful to my slightly shy and introverted self. I'd much rather go hiking or something.
I'm not concerned with them - I'm just explaining why dating apps suck.
I'm also not casting a curse on anyone, you misunderstood. I'm not saying I'm better than them so this doesn't happen to me. No, it also happens to me.
Because this is by design. This is systemic. The apps are designed in such a way to make your expectations unrealistic and thereby perpetually let you down, because that's how you continue to use the app!
Apart from the fact that IQ tests are racist bunk, there's no need to do some fancy self-discovery journey or anything to determine whether you're cut out for pure math or not: if you have to ask, then it's not for you.
I think the idea that Lisp was so much more productive than other languages originates from a much earlier time. But now the most important features of Lisp - like garbage collection - are commonly available in most languages.