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

91–100 of 117 posts

Re: Slack Code

#91

Post by throwaway-blaze »

sph wrote: post #62
paxys wrote: post #16

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 like writing code too. What I don't like doing is debugging code that just isn't doing what I want. Debugging CSS layout issues in Safari vs Chrome vs Firefox? Screw that...agent do it. Debugging layout issues in a React Native mobile app on Android on that one weird screen layout phone? Screw that....agent do it.

Re: Slack Code

#92

Post by apetresc »

altmanaltman wrote: post #50
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

Do you mean Teams + Claude? Because Teams and GitHub have had plenty of integration with each other for years.

Re: Slack Code

#93

Post by vips7L »

tuesdaynight wrote: post #77
sph wrote: post #70

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.

Yes they will.

Re: Slack Code

#94

Post by vips7L »

lbreakjai wrote: post #45
tayo42 wrote: post #31

Earlier quoted context omitted.

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.

Can’t get left behind by people who can’t write a crud endpoint or an email by themselves.

Re: Slack Code

#95

Post by dmd »

toomuchtodo wrote: post #54
cavem0nkey wrote: post #25

Earlier quoted context omitted.

Same here. All I do now is spend all day on calls with people whose shit exploded and I'm trying to scrub it off the walls, ceiling and the customers.

All money is green. Ensure you are being compensated sufficiently for your time.

Most of the world’s money is not, in fact, green.

Re: Slack Code

#96

Post by anabis »

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…

I think they have Teams bot, but it's bound to a particular user.

Re: Slack Code

#98

Post by nlawalker »

darkstar999 wrote: post #79
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.

I can’t hear what they’re saying, they drop the mic every other sentence!

Re: Slack Code

#100

Post by syspec »

Etheryte wrote: post #12
lapkaaaa wrote: post #3

But why, it brings literally nothing to the table

This is the easiest sell of the century, product can discuss and implement changes without ever getting engineering involved. Or at least that's the theory, I think everyone here can think of a number of reasons to have reservations on this front.

In what? Like changing the color of the button of a website? How does that render in situ? For anything meaningful you need a preview environment
Post reply on HN