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

Command line functions around OpenAI

kadekillary.work

Post reply on HN
Print view View original

131–140 of 316 posts

Re: Command line functions around OpenAI

#131

Post by bckr »

Alex3917 wrote: post #119
roenxi wrote: post #10

Being efficient at writing code can barely make someone a 5x engineer. A team of people who write code effectively is easy to do. Hyperproductivity in software is all about deciding what problems to tackle. Richard Hipp isn't worried about chipotle restaurant orders in golang, he's worried about how to store data reliably. That isn't a coding puzzle that ChatGTP is likely to help with. Either ChatGTP can do the whole…

> Being efficient at writing code can barely make someone a 5x engineer. In a winner-take-all economy, usually the winner is the person with the ability to do something the slowest. Not always, but usually.

Say more

Re: Command line functions around OpenAI

#132

Post by grogenaut »

b7r6 wrote: post #95
roenxi wrote: post #10

Being efficient at writing code can barely make someone a 5x engineer. A team of people who write code effectively is easy to do. Hyperproductivity in software is all about deciding what problems to tackle. Richard Hipp isn't worried about chipotle restaurant orders in golang, he's worried about how to store data reliably. That isn't a coding puzzle that ChatGTP is likely to help with. Either ChatGTP can do the whole…

I'm aware that I'm in the minority here, but I find that investing heavily in being able to type fast and handle the tools well actually changes what code I write and not just how quickly. The faster I've gotten at moving code around, the more subconsciously willing I've been to try something with a modest probability of working out, and more importantly the easier it's gotten to throw away a draft that isn't working…

I think this is true but I also found limiting returns on going faster and at some point your just confident enough to try out if it is a good idea. It also becomes easier to justify, you become more trusted and you evaluate better.

Maybe that makes everyone hit that point easier, maybe it brings that point in for you. Not sure.

Re: Command line functions around OpenAI

#133

Post by grogenaut »

davnicwil wrote: post #87
dasil003 wrote: post #54

Earlier quoted context omitted.

The GP is undermining their own point by even mentioning “5x, opening the door to think about this in linear terms. But the concept of a “10x engineer” was never about how fast they produce code, and the multiplier was never a fixed number. The point was that some engineers can choose the right problems and solve them in a way which the majority would never achieve even with unlimited time. As an example, if you took…

Maybe in 2030 the AI will be able to respond to that situation appropriately, like it won't just layer more sticky plasters on top with each additional requirement and make a mess but will re-evaluate the entire history of instructions and rearchitect/refactor the code completely if necessary? And all this with documentation explaining what it did, and optimising the code for human readability, so that even with huge…

Maybe the prompt engineer will learn from the conversation and remove their dead end questions. Every time you ask a question gpt is just re running it all includinG the previous context. If you start over with a trimmed conversation it's like the player was never there.

Re: Command line functions around OpenAI

#134

Post by [deleted] »

ChrisBland wrote: post #61

Writing code is the basic 101 of our industry. Anyone can write a loop or an if statement. With todays computing power, for most applications even poorly written code will run and will execute quite fast. What makes someone a 10x (and i hate that term) is the ability to take requirements, or better yet, a vague idea given to them by the business and turn that into software that benefits the end user and makes the com…

[deleted]

Re: Command line functions around OpenAI

#135

Post by californical »

yosito wrote: post #113

A lot of people seem to be hung up on the title and totally missing how useful this tool is. People are right that the tasks that you're having this tool do aren't tasks that a 10x (or 1000x) developer would do. But what they're missing is that this is exactly why you can use this tool to multiply your productivity. If you don't have to spend your time writing silly scripts anymore or converting JSON to yaml or whate…

It possibly enables you to build the wrong thing, 10x faster.

Do you think the company will let you just have fun learning for the other 90% of the time that you can free up? They’ll just expect more output. Being able to write code 10x faster will likely not free your time enough to become a 10x problem solver.

Re: Command line functions around OpenAI

#136

Post by grogenaut »

bckr wrote: post #131
Alex3917 wrote: post #119

Earlier quoted context omitted.

> Being efficient at writing code can barely make someone a 5x engineer. In a winner-take-all economy, usually the winner is the person with the ability to do something the slowest. Not always, but usually.

Say more

As the winner they are going to have the luxury of taking a few weeks to get back to you on this one

Re: Command line functions around OpenAI

#137

Post by [deleted] »

b7r6 wrote: post #95
roenxi wrote: post #10

Being efficient at writing code can barely make someone a 5x engineer. A team of people who write code effectively is easy to do. Hyperproductivity in software is all about deciding what problems to tackle. Richard Hipp isn't worried about chipotle restaurant orders in golang, he's worried about how to store data reliably. That isn't a coding puzzle that ChatGTP is likely to help with. Either ChatGTP can do the whole…

I'm aware that I'm in the minority here, but I find that investing heavily in being able to type fast and handle the tools well actually changes what code I write and not just how quickly. The faster I've gotten at moving code around, the more subconsciously willing I've been to try something with a modest probability of working out, and more importantly the easier it's gotten to throw away a draft that isn't working…

[deleted]

Re: Command line functions around OpenAI

#138

Post by m3kw9 »

Nevermark wrote: post #84
austin-cheney wrote: post #43

Earlier quoted context omitted.

Define “efficient at writing code”. I find that for many people this means something primitive and absurd like typing faster or remembering things better. Being efficient in the perspective of writing new automation so you don’t have to do the same manual things again can easily make someone a 10x (or greater) engineer. This typically means writing your own tools and not hoping some third party package or framework w…

I agree with the compounding impact of self-automation. Also, some people just keep growing their creative outlook. They are not afraid to try solving bigger & bigger problems. I worked with an engineer (individual contributor) at a company with a lot of related software products. Time and again, he would hibernate then come out with a new well developed tool or product that either impacted the entire product line or…

Yeah a traditional 10x engineer would know how to create/use leverage to enable much more work to be done faster in this case creating a great tool, reminds me about a car mechanic how he showed me this weird tool and said it was one of the most useful tool he’s fashioned

Re: Command line functions around OpenAI

#139

Post by quadcore »

roenxi wrote: post #10

Being efficient at writing code can barely make someone a 5x engineer. A team of people who write code effectively is easy to do. Hyperproductivity in software is all about deciding what problems to tackle. Richard Hipp isn't worried about chipotle restaurant orders in golang, he's worried about how to store data reliably. That isn't a coding puzzle that ChatGTP is likely to help with. Either ChatGTP can do the whole…

Indeed it's not about what you type, it's about what you don't.

Re: Command line functions around OpenAI

#140

Post by grogenaut »

nolawi89 wrote: post #128
Lewton wrote: post #41

Earlier quoted context omitted.

ChatGPT will turn your day into spending 90% of your time reviewing code...

what do you mean? Do you mean that there is infinite amount of code because its also writing so much code?

Because people will generate more crap and throw it at you as the quality control. They'll have less knowledge overall as they cede more to chat GPT. Also your impact will be in cr, so they'll send you more people. You get faster and more responsive using chat GPT to review, so you'll do more reviews, causing people to send more frequent ones to get your feedback faster. Eventually just hire some interns to toss plausible shit at gpt and then you. Fire the ftes. Done.
Post reply on HN