Live data from Hacker News

Command line functions around OpenAI

kadekillary.work

51–60 of 316 posts

Re: Command line functions around OpenAI

#51
post #6

> First off, you’ll need an OpenAI API key. You can get this by going here and signing up. Note that you'll also need to be from a Western country, or at least have access to both a phone number from one and a VPN. And if you want a plus subscription, you'll also need a US credit card - not stated anywhere but I've been totally unable to sign up for plus with either Irish or Belgium cards, it just immediately flashes…

Sign up for the api, they only start charging end of month.

Re: Command line functions around OpenAI

#53

Anyone know best way to punch up his function a little so it tees >> out both the q and a to a file? Like history but for chat gpt.

I don't, but you may be interested in something that improves upon that with the history optionally in outline format:

https://github.com/rksm/org-ai

Re: Command line functions around OpenAI

#54
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…

Writing code quickly may not help the mythical 10x engineer, but it might help a 1x engineer become a 5x engineer. In relative terms, the unaided 10x engineer is now only a 2x engineer as his peers are now vastly more productive. That's huge.

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 away the top half of the engineers on my current team and gave the rest state of the art Copilot (or equivalent best in breed) from 2030, you would not end up with equivalent productivity. What would happen is they would paint themselves into a corner of technical debt faster until they couldn’t write any more code (assisted or unassisted) without creating more bugs than they were solving with each change.

That doesn’t mean the improved tooling isn’t important, but it’s more akin to being a touch typist, or using a modern debugger. It improves your workflow but it doesn’t make you a better software engineer.

Re: Command line functions around OpenAI

#55
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 agree with your sentiment. I've generally advanced in my career by being good at deciding what problems to solve/not solve.

The problem is many, many people are not in a position to advance that way. I've worked in startups where you're almost always given an ambiguous problem and rewarded for meaningful outcomes.

Many people are working as part of team/projects where the general problem and approach are already determined for them.

Re: Command line functions around OpenAI

#57
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…

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…

> they will just be average or much worse when their motivation is destroyed

Ouch

Re: Command line functions around OpenAI

#60

There seems to be a lot of dissenting opinion on how these tools will affect software engineering jobs. Those of us that have deep architectural skills, are able to deal with ambiguous requirements, balance UX with technical limitations, etc, will be safe for a good while. Those of us that were trained in bootcamps to crank out MEAN/MERN/etc apps might be in a bit of trouble. I say this not to disparage the latter gr…

Question is whether you have to go through the bootcamp stage to become an architect? Like many skills, you often start with the simple stuff.

Yeah I'm wondering the same thing. How do we train up the next generation of SWEs given the new world we live in?

Interesting times.

Post reply on HN