I see your point, but can’t square it.

If he had said “I didn’t think it mattered so I didn’t think to tell her” that would make sense, but the fact that he said he deliberately hid it (ie harmless secret) means he knew she wouldn’t like it. Which makes sense because I think it would be pretty common to get “no” for an answer when you ask your spouse if you can name your kid after a bug.

There’s nothing wrong with bugs. It’s all about intent, and he clearly intended to hide this from her because he knew (correctly) it would be a problem for her. So it was a lie by withholding relevant information. About their daughters name. Its messed up. It’s also dumb because it’s so easy to look up the origin of a name that this “secret” isn’t really one at all.

Poes law

I was an engineer is school. I’ve always been good at fluffing up my writing, but it always annoyed me that I had to make things longer when I felt like I was already done.

When one of my first engineering reports said “this has to be no more than 2 pages long” as opposed to “at least” I knew I had chosen the right school. Lol

but for beginners? They will have a lot of bugs in their code.

Everyone has lots of bugs in their code, especially beginners. This is why we have testing and qa and processes to minimize the risk of bugs. As the saying goes, “the good news about computers is that they do what you tell them to do. The bad n was is that they do what you tell them to do.”

Programming is an iterative process where you do something, it doesn’t work, and then you give it another go. It’s not something that senior devs get right on the first try, while beginners have to try many times. It’s just that senior devs have seen a lot more so have a better understanding of why it probably went wrong, and maybe can avoid some more common pitfalls the first time around. But if you are writing bug free code in your first pass, well you’re a way better programmer than anyone I’ve met.

Ai is just another tool to make this happen. Sure, it’s not always the tool for the job, just like IoC is not always the right tool for the job. But it’s nice to have it and sometimes it makes things much easier.

Like just now I was debugging a large SQL query. I popped it into copilot, asked if to break it into parts so I could debug. It gave a series of smaller queries that I then used to find the point where it fell apart. This is something that would have taken me at least a half hour of tedious boring work, fixed in 5 minutes.

Also for writing scripts. I want some data formatted so it was easier to read? No problem, it will spit out a script that gets me 90% of the way there in seconds. Do I have to refine it? Absolutely. But if I wrote it myself, not being super prolific with python, it would have taken me a half hour to get the structure in place, and then I still would have had to refine it because I don’t produce perfect code the first time around. And it comments the scripts, which I rarely do.

What also amazes me is that sometimes it will spit out code and I’ll be like “woah I didn’t even know you could do that” and so I learned a new technique. It has a very deep “understanding” of the syntax and fundamentals of the language.

Again, I find it shocking that experienced devs don’t find it useful. Not living up to the hype I get. But not seeing it as a productivity boosting tool is a real head scratcher to me. Granted, I’m no rockstar dev, and maybe you are, but I’ve seen a lot of shit in my day and understand that I’m legitimately a senior dev.

And before stack overflow, we used books. Did we need it? No. But stack overflow was an improvement so we moved to that.

In many ways, ai is an improvement on stack overflow. I feel bad for people who refuse to see it, because they’re missing out on a useful and powerful tool.

Can I get a citation on this? Because it doesn’t pass the sniff test for me. https://en.wikipedia.org/wiki/Approximation

deleted by creator

I think the … here is meant to represent repeating digits.

Which is, of course, true for every source of information that can point you in a direction.

I’m a senior dev, and copilot as a productivity tool usually pays for the monthly license multiple times per week.

Whenever I hear someone say it’s useless, that tells me they are either some godlike dev who knows everything already (lol), they haven’t actually used it, they are not good at integrating new tools into their workflow, or they simply haven’t learned how to use it yet.

I don’t consider myself a never nester, but looking at my code now, I extract all the time and rarely go 4 tabs in. It just makes it more easily maintainable. I also like the idea of putting the failure conditions first. I haven’t looked at this yet but I’m sure there are some times I can use it.

Sure, sometimes you might not have a choice, but I do think there is a lot of value to what they are saying. I think it kind of goes in line with standard “functions should do one thing” paradigm.

I’m the article they point to a lot of factors as to why this is now becoming an issue: increase urbanization, increased industries, increased tourism.

They do say collecting rainwater is probably part of the solution, but if the other things keep on growing that won’t always be the case.

The other poster is either speaking from a place of ignorance, as they’ve never really used it, of they just aren’t smart enough to learn how to use a new tool.

As much as middle management sucks, devs blaming management for their own inability to learn is almost on the same level.

I was lucky enough to get in on my company’s beta test for copilot.

When I hear people say it’s bad, all that tells me is that they are either completely ignorant and have never really used it, or they aren’t good at learning how to use new tools.

I’ve worked in a few places, all with senior engineers, including myself as a senior engineer, all of which the senior engineers spent most of their time actually engineering. If I went somewhere as a senior and was told I was going to be in meetings all day, I would quit because that’s management, not engineering.

We do standups twice a week. At worst they run a half hour for my team of about 10 people. Usually we’re done in 15-20 minutes. Please tell me it’s just an absolutely made up joke that you have an hour and 15 minutes of stand up meetings every day. I would shoot myself.

One of my biggest pet peeves is when someone uses multiple question marks at the end of a statement. I’m triggered right now and reporting you for harassment. Lol

I haven’t taught my kids. . .yet.

However, they know that if they can’t find something they want to watch, they just have to ask me and I’ll get it from them. . .and that (sarcastically) “daddy is just borrowing it from the internet” so I think know what’s going on.

My 100 year old house has marks on the floor that look like it was worn from a door swinging. Very distinctive arc pattern. Like it was there for many years and was under frequent use.

The problem is that there’s no door there, just a wall, which is also the edge of a dormer…so if there were a door there it would just open out onto a sloping roof.

Every time I register it I contemplate why it’s there and wtf happened.