Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Slack Code

salesforce.com

Post reply on HN
Print view View original

41–50 of 117 posts

Re: Slack Code

#41

Post by cavem0nkey »

abixb wrote: post #11

SaaS companies have run out of ideas. No one truly needs another coding agent. I weep for SaaS's future.

SaaS companies never had any ideas in the first place past turning a one off software cost into a monthly one and making you an addict of their crack supply. The coding agent just puts them between you and getting shit done again so they can monetize it. Milk you dry.

Seriously just fuck the whole industry and walk away! Go back to emailing spreadsheets and documents around. Save your shit to your own hard disk. You don't need a todo app - just post-its stuck to your fucking monitor. Call someone on the fucking phone. Crack your software or use OSS. Run it all on recycled PCs. Stop giving everyone money for this shit because it's only normalising your subscription future.

Note: I work for a SaaS company. They are bastards. They all are.

Re: Slack Code

#42

Post by abtinf »

arscan wrote: post #8

> 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.

Every sentence on that page reads as slop.

Re: Slack Code

#43

Post by notpushkin »

ZeroCool2u wrote: post #38

I'm shocked Teams + GitHub haven't already done something like this. But I suppose that's asking a lot from Teams. I've been using Claude and other agents in Slack for some code tasks. It's mostly fine for simpler projects and products. Things like docs or specific libraries. But I'm not really convinced this is the ideal interface yet. Reviews are my bottleneck and GitHub has a great UI for this. Plus, token consump…

GitHub has bigger problems at hand. The uptime won’t plummet by itself!

Re: Slack Code

#44

Post by drfritznunkie »

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 generous and allow you to renew at a slightly discounted rate, subject to the approval of our deal desk, of course ". barf.

Re: Slack Code

#45

Post by lbreakjai »

tayo42 wrote: post #31
sph wrote: post #10

At this point I literally have no idea what modern coding is supposed to look like. I still open my editor, type stuff in and run make. All these tools are released daily and they just fly over my caveman head.

I feel like theres so much churn and change there's no point in trying to keep up.

Remember six months ago when linkedin people were adamant you needed to keep on top of everything not to get "left behind"? Agents, skills, mcps, swarms ...

If anything, my setup has gotten ever so simpler as models got better.

Re: Slack Code

#46

Post by noodletheworld »

What even is this feature?

You can’t just “spin Claude up in slack”; it can’t magically just connect to GitHub and your code.

I presume this feature basically is like… if you’re already using your agents in cloud hosted runtimes, then you can connect to those agents like you already are, but via slack.

…

Did I misunderstand?

This seems like a non feature; if you’re bring to want it, you can’t have it because you have to setup Complicated External System, and if you’re already using cloud hosted agents, you’re already using it (eg. Claude tag or whatever).

So it’s what… a diff viewer in slack? An agents tab so slack becomes like cursor?

The videos seem enormously light on examples of how it actually works, did someone find a more detailed example of usage to show why you want this?

Re: Slack Code

#47

Post by ramoz »

ericpauley wrote: post #28

I'm going to chock this one up as a yet-another "X is your agentic coding hub" PR nonsense. What are people actually using to manage semi-collaborative agentic coding workflows nowadays? We've moved from on-dev-machine coding to @claude in GitHub, but of course GitHub purposefully weakens the capability of that approach to the point that it's kind of a hack. Github/Linear have somewhat more cohesive experiences but i…

Why did you move from on-dev-machine coding to @claude in GitHub if it's a weaker capability?

Im not convinced of any of these cloud or tagging solutions where I get to the point of moving coding away from my dev's machines.

Re: Slack Code

#48

Post by gk1 »

lapkaaaa wrote: post #3

But why, it brings literally nothing to the table

Slack wants to be primary place people do their work. And they're almost there... It's certainly where you "work" (communicate) with people, it's where many engage with and/or control other platform like project trackers, and it's increasingly the place you interact with whatever AI agents your company uses. It makes perfect send they want to bring the coding agent into the fold (into their UI) as well. And, given Anthropic's release of Claude Tag, they're probably not wrong about that.

Re: Slack Code

#49

Post by johnsmith1840 »

skywhopper wrote: post #19
sph wrote: post #10

At this point I literally have no idea what modern coding is supposed to look like. I still open my editor, type stuff in and run make. All these tools are released daily and they just fly over my caveman head.

That’s fine, and you’re doing fine. In fact, in a few years you will probably be far more skilled than most “software engineers”.

I dunno dude, it's getting scary fast. You tried a fable/5.6sol maximum effort on a chunky task yet?

Maybe in a few years being a good coder will be like being a good taxi driver with self driving. You know the best spots and the ai can't drive the most unusual roads but effectively 95% of all driving is self driving.

Re: Slack Code

#50

Post by altmanaltman »

ZeroCool2u wrote: post #38

I'm shocked Teams + GitHub haven't already done something like this. But I suppose that's asking a lot from Teams. I've been using Claude and other agents in Slack for some code tasks. It's mostly fine for simpler projects and products. Things like docs or specific libraries. But I'm not really convinced this is the ideal interface yet. Reviews are my bottleneck and GitHub has a great UI for this. Plus, token consump…

God Teams + Github would be a hell within a hell
Post reply on HN