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

31–40 of 117 posts

Re: Slack Code

#31

Post by tayo42 »

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.

Re: Slack Code

#33

Post by dewey »

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

Or unemployed, the jury on that is still out.

Re: Slack Code

#35

Post by wolttam »

This is probably getting close to the right interface for these things, and that's coming from someone who is religious about using terminals, neovim, etc.

Re: Slack Code

#36

Post by ghm2199 »

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.

The collective harm that this kind of language does to a human skill of writing by oneself is probably immeasurable (that is until some clever social science researcher finds a controlled way to quantifying this).

The full statement:

> This isn't just a new feature — it’s a new way to build software: open, collaborative, and powered by both human ingenuity and judgement and agent scale. Teams that build this way won't just move faster. They'll build things no one else can.

I am not sure how just drawing contrasts between two things without actually drawing any kind of causal relationship to explain _why_ something is better or _how_ it does it, came to be a good thing. It is the kind of vaccuous statement that some poor tired sod with his remaining system 1 capacity just YOLOd into the blogoshpere and, like you said, the weary who don't know any better get FOMOed by. PSA: you arent missing anything.

Re: Slack Code

#38

Post by ZeroCool2u »

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 consumption with Slack is out of control.

Maybe in time this will be the way we work, but for now I still find myself using GitHub, a terminal, and slack together.

Re: Slack Code

#39

Post by namarie »

dewey wrote: post #33
skywhopper wrote: post #19

Earlier quoted context omitted.

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

Or unemployed, the jury on that is still out.

Or both?

Re: Slack Code

#40

Post by Retr0id »

Looks like a great way to replicate the setup of "four guys standing around watching one guy do the work" but the one guy is Claude now.
Post reply on HN