101–110 of 117 posts
Earlier quoted context omitted.
I used to be that person, and suddenly I haven’t opened an editor or written a line of code by hand in 6+ months.
But why? I like writing code. Why in the world would I want to become someone that doesn't write code?
I still like reviewing code, but I don’t need to physically write it
Earlier quoted context omitted.
I do care about my enjoyment. Or should my existence, wants and dreams solely be defined by my current employer? Are yours?
I don't understand what you want to hear. You can still code manually all you want, but people will not pay you for doing that in the near future. You can still do it for your personal projects.
Interjecting, here. Perhaps not an academic repeat of five years ago; is this an eon for Technology or not long enough? I've lost track. Anyway, I appreciate the optimism.
An anecdote, from the ground floor: this industry has shown it's paying leagues of on-site hands to install systems, at scale, from USB keys. PXE products have existed for decades; we're writing one [to adopt] when we could take one off the shelf. These artisanal OS installations are too rich for my blood. Or, they would be, if this modernization didn't happen to be the code I'm still writing by hand. Half a decade in (or several) depending on perspective.
I'll believe things are progressing as you say... when this type of mismanagement stops happening like clockwork. Want more chatbots/datacenters? Catch up to the mid-1980s; BOOTP 'just' dropped.
Oh great, I look forward to our next Slack renewal when they foist another 125% licensing increase on us for yet another AI add-on we don't want. This year, they decided that our Enterprise plan wasn't paying for another floor on Benhioff's tower fast enough and so forced an 125% license increase. They then played the game of "if you renew early, we're going to cut you a special one-time deal because we're feeling ge…
Earlier quoted context omitted.
I think you might be taking that number a bit too literally. What I mean is, it works enough that no one is complaining. But, all software has bugs. Some are logic/syntax bugs, and some are intent . "It should do this, but actually does that ." The sum of ALL of these classes of bugs is such that our clients haven't complained about the software being particularly faulty. It's impossible to tell if it's more or less…
I'm with you on this. It feels like it should matter, but everything is pointing to "it doesn't matter as much as you guys say that it matters". I had the same experience at work. I thought we would have way more bugs and problems, yet all I see is the same as ever, but faster. It's eye-opening, honestly
Oh great, I look forward to our next Slack renewal when they foist another 125% licensing increase on us for yet another AI add-on we don't want. This year, they decided that our Enterprise plan wasn't paying for another floor on Benhioff's tower fast enough and so forced an 125% license increase. They then played the game of "if you renew early, we're going to cut you a special one-time deal because we're feeling ge…
and you're still paying for it so why complain?
We don't need this, just add syntax highlighting in code blocks.
https://docs.slack.dev/reference/block-kit/block-elements/ri...
admittedly i don't think there's a way for humans to do it through the ui currently yet, e.g.,
@@@ ```lang foo ``` @@@
Earlier quoted context omitted.
and you're still paying for it so why complain?
It's always amazing to me how everyone continues to pay a fairly ridiculous price for Slack. Sure it has it's issues but I think people would get used to it and be just as productive with the free Google Chat they already have if any executive had the guts to say they're not going to waste money on Slack anymore. But never happens.
My friends in knowledge-worker America tell me that they are stuck between two megacorp visions of the workplace: 365/Teams/Copilot and Salesforce/Slack. Each wants to own the whole stack, but cannot. Workers are stuck with two systems that dont want to talk to one another.
> This isn't just a new feature — it’s a new way to build software I imagine they smushed 2 of the most well-known AI-isms together on purpose here to troll the AI-weary. Might as well I guess, if this type of language annoys you then the whole feature probably will too.
Earlier quoted context omitted.
It's always amazing to me how everyone continues to pay a fairly ridiculous price for Slack. Sure it has it's issues but I think people would get used to it and be just as productive with the free Google Chat they already have if any executive had the guts to say they're not going to waste money on Slack anymore. But never happens.
If your enterprise is one of those corporate fortune 500 types that has Salesforce, you basically have to have Slack as it's the easiest, fastest, or at least the least miserable way of interacting with Salesforce. My friends in knowledge-worker America tell me that they are stuck between two megacorp visions of the workplace: 365/Teams/Copilot and Salesforce/Slack. Each wants to own the whole stack, but cannot. Work…
One one hand, it sucks having to monitor two services.
On another hand, it is nice having “corporate bullshit” constrained to teams.
The styles of communications / culture are very different between the two systems.