You know what I’m saying? I have zero interest in using AI to code. It’s taking all the fun out of coding and leaving me with only the boring parts.
plus more of the boring paets and over time less good documentation
I feel the opposite, AI allows me to think more about high level tradeoffs and design as opposed to actually coding which is meh.
I assume you don’t do this for a living then. We who chose this line of work I think actually usually enjoy the coding.
At least moreso than reviewing and fixing other people’s bad code.
But it’s not like we don’t do those fun things you mentioned, too. You first think of a design, investigate the high level trade-offs, iterate, brainstorm, repeat. Then you code a bit, then start over and see if what you did works, and circle back. The coding part is the smallest part IME.
So I don’t get this whole “AI lets me do other things”. AI for me takes up the same time as it would’ve taken me to do it myself, because learning the code output, reviewing it, refactoring, and fixing shit takes so much time compared to just doing it, that it’s at least equally time consuming. And leaves me with the boring bits.
Coding is a craft, and I enjoy my craft. 🤷♂️
@Not_mikey@lemmy.dbzer0.com it’s the same for me and i suspect that the way the down/upvotes for your comment have played out and that of @victorz@lemmy.world is indicative of the software engineering field’s proclivities of today.
my decade as a software engineer gave me the awareness that its most outspoken practitioners voice a viewpoint along the same vein as that @victorz@lemmy.world shared – as artisans working at their craft – and i think it lays bare their background and how they see the world and themselves in it.
my time in the field also gave me an anecdotal awareness of how popular the sentiment is despite an overwhelming majority not embracing it until influenced. in my later years in the field, several other engineers and i took it upon ourselves to formally train fresh graduates because we collectively became aware of the gaps between academia and the needs of our old-silicon employer.
i was the first to teach them because most were slated for operations roles and i was also the last because i was on the team responsible for new pushes to production. the other engineers and i agreed to this pattern because my decade+ of IT experience lent to a role more closely involved in day-to-day operations than my colleagues who did nothing other than software development.
for 6 years and without fail, the “students” at the first almost-week long bootcamp saw the work the same way i did – as ordinary technical work that’s skilled but not sacred or unique. after they spent the following almost-2-weeks with my colleagues and then returned to me for the final few days of company specific training, they began espousing this artisan perspective, the same as most of my colleagues had before them.
i shared this observation with the only other colleague that had a background and make up that was different than the others. she called herself an engineer like i did and she called my observation the “geek industrial complex”. she had been a software engineer since the 1990’s and told me about red hat’s “geek world” contest – a marketing facade based on the popular-at-the-time mtv show named “real world”. she said people calling themselves “artisans” or “craftsmen” instead of engineers was the same playbook: manufacturing a romantic identity to sell back to people who bought in, leading them to often gatekeep against others to prove their own authenticity. she said it was how they coped with being cogs while convincing themselves they were something more – a labor aristocracy that clocked in just like everyone else does.
i wasn’t sure what to make of it at first, but i started studying leftist politics not long afterwards and everything i’ve read & watched since then has reaffirmed to me that she was right.
When you’re working on a big enough project, you’ll inevitably find yourself acting as a condom between people who don’t understand your niche field and the thing you’re all building together.
That’s not unique to Claude. However, the fact that Claude can drop big salty loads far faster than you can catch them does present additional challenges.
Username relevant 👌
It’s always been my fantasy to be simultaneously inside some pussy and filled with cum.
Mr. Doctor weker that’s fucked up (or down, depending on your sex position)
It’s really easy with a threesome
C^um^ ++
Lol, but also what is that watch? It has a strap over the face?
It indeed looks like a whoop.
Tf is the point of this?? Am I old now??
It’s probably a fitness band, see fitbit air, or whoop, and I’m sure there are more
I’ve long thought that the next step of watch evolution is for them to stop actually telling time. They’re just a fashion item already – even people with watches check their phone for the time.
So I think, over time, the actual watch face will become rather vestigial. At first, no longer worrying about whether the hands actually point to the correct time. Then, not bothering with having them move at all. And maybe, ultimately, getting rid of the watch face entirely and just having a bracelet.
My watch is actually a small bag of holding which I use to carry my tic tacs. 200 candies per container, 12 containers per pack. I’ve been pouring them into my watch in bulk. I tend to eat them by the handful while I’m working or gaming, so in a day I can easily slam through 1-2 containers worth.
Do people study “Software Engineering”?
Usually you study Computer Science.
We had a class called Software Engineering, but it was more about the business process, project management, QA, docs.
I met someone once who was attending a trade school for some degree or certification or something in “Software Engineering Management.” And this dude wanted to try talking shop with me lol.
Those are people who probably should be the condom between clod and prod.
I know people with degrees in software engineering. CS is not the same thing as software engineering. CS includes more theoretical and mathematical stuff whereas software eng is about the practice.
My bachelor’s was actually called Software Engineering (it was 10 years ago, so it migh’ve changed a lot), on Faculty of IT. It was mostly just applied programming (but also indepth - from assembly through smalltalk, to bash, C and Prolog), with a lot of courses about SDLC, UML, DevOps, and all that.
We also had a lot of advanced math, from integrals to logic, and some CS like data structures, algorithms and all that jazz.
It was not as theoretical as actual Computer Science on other faculties, and was more devops oriented, but I did learn a lot of fundamentals about every language I can imagine, including lambda calcul, and also all the math I could ever need. And I’m pretty glad I was forced to learn about proper processes, am able to read and correctly design an UML, and have some insight into various types of the SDLC - which apparently isn’t that common, judging by my experience when actually working. Not that it ever matters - all it ever got me was being internally annoyed that people are using/doing it wrong, but it’s not a big deal because everyone understands eachother, and there’s no reason to point it out and be smug about it.
But yeah, CS was mentioned a lot, but the difference was mostly that CS is theoretical and way more math heavy, while SWI is pretty similar in most of the circulum, but instead of obscure theoretical proofs about big O of algorithms, you are learning about UML and SDLC.
Also, I got to do an Ethical Hacking optional course, which landed me a job in cybersec and started my carrier (before I moved to gamedev), so that’s also nice.
In general, it gave me a lot of “technical soft skills”, it was also team project oriented and asked us to have all the requirements and documentations and architecture designs 100% formally written, and that is a really good skill to have.
Comp sci and software engineering are 70% the same, the difference is CS is more math and theory oriented, software engineering is hogher level and more about methodologies, software architecture, systems design.
(Consider any other science discipline vs. Engineering discipline)
I did an MSc in Computer Engineering. my uni also had computer science, but it was only a BSc and they did more theoretical stuff. We built hardware, debugged assembly, and studied signal propagation, while they looked at ACID compliance, data deduplication, and high-level architecture. well, we did that too but much less of it.
It’s generally very similar, just that in compsci you can usually do some elective papers as part of the degree, whereas for engineering you have to do prescribed engineering ones.
Back in the day it was CompSci, or Electrical Engineering. I don’t know if they’ve really started teaching actual software engineering yet or not, back in the day it was a bunch of theory that’s mostly just foundational stuff that you don’t really interact with day to day anymore. In other words: academia was 10+ years behind industry, which is pretty typical, but not such a problem in a field like Irish Literature as it is in software engineering.
