You wouldn't mind writing machine code then? Ok, I'll give you assembly. It's all that's needed to tell a computer what to do.
It's definitely for humans first and computers second. Compiled, machine code is for computers, everything else are tools so that humans don't have to deal with machine code. An abstraction made by humans for humans to use.
This is one of the issues I see with LLMs for code: instead of engineering and leveraging machine learning for optimizing specific problems, we're now forcing text prediction engines to write human oriented text that happens to be a programming language.
So this is not as bad as some of the other stories I've seen, but I'll bite.
It was an old .NET Framework MVC app. Some internal product management system or something. There was a need to do a PDF export in one of the use cases, so someone implemented it. It wasn't a good implementation: one big controller, mixing UI and business logic, etc. However, it basically came down to a single private method in a specific controller for a page.
Now time passes and lo and behold, we need a PDF export in another page for a different use case. "No problem," - same dev, probably - "I already solved this problem. I'll just reuse the PDF generation logic."
Now, any sane person would probably try to refactor the code responsible for PDF stuff into a separate service (class) and reuse it. A less sane, but somewhat, acceptable approach would have been to just copy paste the thing into another controller and call it a day.
Ha! No no no no no no… Copy pasting is bad, code should be reused…
The end solution: REFLECTION. So the dev decided that the easiest way to make it work was to: 1) use reflection to inject one controller into another; 2) then use reflection again to get access and call that private method for PDF rendering into a stream.
Fortunately I didn't have to fix that fragile mess. But I did my fair share of DevExpress corpse hacking and horrible angular "server side rendering" workarounds.
Security through obscurity is not security. I see no reason why source maps should be unavailable.
Yeah, this. Code for the problem you're solving now, think about the problems of the future.
Knowing OOP principles and patterns is just a tool. If you're driving nails you're fine with a hammer, if you're cooking an egg I doubt a hammer is necessary.
0r something similar along that line.
I'm really bothered by that zero 0 instead of an o O.
Won't anyone think of the shareholder value!
That snail that will kill you on touch just got an upgrade.
What am I looking at?
I just need to compose my will to get up. Then it's coffee brewing ritual.
Notification syncing between devices is nonexistent in Teams and there are no conversation threads.
In general teams is way more buggy with worse UX. I don't know if it's a thing on Teams that our workplace disabled, but there's no decent notification management. If I take a day off, I can set my notifications in Slack as mute for that day and I can manage notifications for messages vs mentions vs mute per channel.
On Teams I can't permanently set Enter as new line, I have to click that rich text editor icon for every single message.
On mobile Teams started doing this thing in group chats where, if I move the cursor with drag on space gesture and then move it back to the end of the message, Teams interprets this as a desire to "attach a program", like power apps (whatever that is).
Pasting in code block also gets me every time. I'll start a code block in Teams window, go to another window, copy the text and click back on my code block. Teams just drops the cursor to the end of message outside my code block and by the time I notice I already hit ctrl+v.
My last pet peeve is about formatted copy pasting and applies to Slack as well but Teams having more text formatting options shows more of an impact. Never, and I repeat, NEVER have I wanted to paste anything with formatting, especially if I grabbed it form a website, word, excel, pdf or a code editor. Why is it the default and nonnegotiable? I can change the default on Libre Office, why not on Teams? It's a chat app why would I need headings like in a regular doc?
Every time it gets me, ctrl+c, ctrl+v, fuck ctrl+z, ctrl+shift+v…
And that is my point. The primary purpose for all these abstractions is for humans to use. It's first and foremost designed to be read and understood by humans, to make programming easier for humans.