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

71–80 of 117 posts

Re: Slack Code

#71

Post by ramoz »

ericpauley wrote: post #61
ramoz wrote: post #47

Earlier quoted context omitted.

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.

Two things: (1) models are far more autonomous and run for longer coherently, (2) visibility into the development process was lost in local development. Because models run for a long time autonomously developers need to manage more agents simultaneously. At that point you basically need a tracker for tasks in flux, and compute for each agent. It also means that the interactive monitoring isn’t as helpful anymore. Reg…

I see. What would the proper solution then look like for when we should consider moving our teams? Sounds like you you said they're all current ones are missing ergonomics. Do you think it's slack code?

Re: Slack Code

#73

Post by dzhiurgis »

It's been obvious for a while Salesforce needs to integrate Slack into Salesforce for engineers.

I spend so much time in slack discussing features. It's obvious it should at least be able to pull orgs metadata.

They already kinda there with agentforce vibes (terrible name), but slack already has nailed chat in general. Having slack bot to collaborate in threads is going to rock.

Re: Slack Code

#74

Post by dzhiurgis »

hi_im_greg_h wrote: post #68
johnsmith1840 wrote: post #49

Earlier quoted context omitted.

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.

Interesting that you use self driving as the metaphor here, when we've been told for years that self driving will be taking over the roads any day now... and yet...

> and yet...

1.5 million people use it for 90%+ of their drives

Re: Slack Code

#75

Post by dzhiurgis »

gk1 wrote: post #48
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 An…

Yeah it's been an obvious pivot for a while now. Airtable kinda has something like this where you can collab with AI and team to build their thing.

Re: Slack Code

#77

Post by tuesdaynight »

sph wrote: post #70
paxys wrote: post #67

Earlier quoted context omitted.

The person paying you doesn’t care about your enjoyment.

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.

Re: Slack Code

#78

Post by tuesdaynight »

adamtaylor_13 wrote: post #60
miyoji wrote: post #53

Earlier quoted context omitted.

> Software works 80-90% of the team exactly as it should. Either you work in a non-standard field, or your standards for software are way too low. What software gets to fail 80% of the time? If your ecommerce checkout software fails 1 in 5 times, you don't have an ecommerce business at all, you are dead in the water. If your airline booking software fails for 1 in 5 customers, you are out of business. 99.99% reliabil…

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

Re: Slack Code

#79

Post by darkstar999 »

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.

> What shows up isn't just messages — it's working code, prototypes, and documents, built right in Slack.

> so building software — from idea to shipped product — isn't just for engineers anymore.

> No ticket, no meeting, no waiting — just a fix, shipped.

> This isn't just a new feature — it’s a new way to build software

It's the same damn structure again and again. It's so gross.

Post reply on HN