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

281–290 of 316 posts

Re: Command line functions around OpenAI

#281

Post by wolfi008 »

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…

We should not forget that different people have different talents. That creative superstar guy may have been great at coming up with new stuff but terrible at maintaining stuff. Or at debugging some urgent prod issue under time stress on a saturday evening. You need those people too that enjoy the day-to-day maintenance to keep the house clean, or the occasional firefighting. A good team contains all those types and they complement each other.

Re: Command line functions around OpenAI

#282

Post by juujian »

throwthrowuknow wrote: post #201
juujian wrote: post #33

Don't get me wrong, this is neat. But the only reason why this works is because there is one million tutorial out there who use this data for teaching new students. The bigger issue is edge cases, stuff where there is no precedence. This output is a starting point for something , but it does not even get you 3% of the way there unless you work for a teenager who is into basketball anecdotes.

It’s also trained on code and books. The knowledge is in there, it just needs more RLHF to improve its abilities. There’s a good chance it can handle those edge cases by combining the information it has in different ways.

If the books have the specific code that is. If the books have some code and discuss edge cases, that is not something a language model could handle. It could give you the abstract concept that applies but it would fail when you prompt it to create new, valid code based on abstract concepts that are in the data.

Re: Command line functions around OpenAI

#283

Post by zamnos »

dang wrote: post #279
senko wrote: post #227

Wow. 210+ comments and maaybe 10 of those actually talk about the article! (yes, I've read them all because I can't believe almost everyone missed the point) The point of the article is actually neat: a small shell (Fish) script to send query to ChatGPT or DALL-E and get response back in the terminal. As a terminal user myself, this is really nice! (I rewrote it for myself in bash which I use, but used the curl comma…

Yes, that's certainly the effect of linkbait titles, which is why HN's guidelines call for changing them: " Please use the original title, unless it is misleading or linkbait; don't editorialize. " If anyone suggests a better title (i.e. accurate and neutral, preferably using representative language from the article), we can change it.

> how to catapult your productivity to the heavens via a series of command line wrapper functions around the OpenAI API.

is in the first paragraph. I think that's too long for HN though, so maybe:

> how to catapult your productivity via command line functions around OpenAI.

Re: Command line functions around OpenAI

#284

Post by gremlinsinc »

tbran wrote: post #278
gremlinsinc wrote: post #243

Earlier quoted context omitted.

I often suffer from impersonator syndrome, my freelance rates should be North if 70 per hour but I keep getting stuck at 40... I grew up poor though and teaching myself coding moved be to earn more then I thought I'd ever earn without a college degree. I knew about for loops almost a decade before I decided web dev would be my career, not just my hobby. it's insane that you could get hired and not know how they work.…

Put your resume up on job sites! Even not-so-great-sounding contracts pay 50-65/hr, might be a confidence boost. Level up your skills on udemy, if necessary (wait for courses to be 80% off or whatever, happens regularly). Could also go corporate at a non-tech for low stress and a decent salary.

I'm actually thinking of pivoting from web dev (10 years a laravel dev) to prompt engineering, and entry-level ai stuff, I'm not going to perfect the next big algorithm, but I can use langchain to create custom KB enhanced chatGPT instances, or automation agents for small-to-mid size companies.

I'm super obsessed lately w/ AI, on youtube, github, HN, reddit, etc... and working on actually building a clone of myself to do the mundane parts I don't like to do... hehe... this is kind of a green field, and the opportunities are huge, might be the last dev jobs when AGI hits -- training custom AGI's...

Re: Command line functions around OpenAI

#285

Post by gremlinsinc »

fzliu wrote: post #273
gremlinsinc wrote: post #255

Earlier quoted context omitted.

> Not mentioned in post this but occured to me by reading: > I think I will start changing my functional prompts to require a JSON format in responses so that various aspects of the response don't need to be manually parsed, and requests can be more reliably piped to subsequent requests. that adds more characters though so maybe hits token limits faster, I was thinking about how to have better contexts then found out…

Beyond artificially increasing prompt length, vector DBs also allow you to inject domain knowledge into autoregressive LMs.

yeah, it's basically like updating the 'cutoff date' on chatGPT but only w/ specific data pertinent to a specific topic, right?

Re: Command line functions around OpenAI

#286

Post by dang »

zamnos wrote: post #283
dang wrote: post #279

Earlier quoted context omitted.

Yes, that's certainly the effect of linkbait titles, which is why HN's guidelines call for changing them: " Please use the original title, unless it is misleading or linkbait; don't editorialize. " If anyone suggests a better title (i.e. accurate and neutral, preferably using representative language from the article), we can change it.

> how to catapult your productivity to the heavens via a series of command line wrapper functions around the OpenAI API. is in the first paragraph. I think that's too long for HN though, so maybe: > how to catapult your productivity via command line functions around OpenAI.

Thanks! "How to catapult your productivity" is still too linkbaity, though. The second half is good. Can you/anyone neutralize the first bit?

Re: Command line functions around OpenAI

#288

Post by fourhourstartup »

dang wrote: post #286
zamnos wrote: post #283

Earlier quoted context omitted.

> how to catapult your productivity to the heavens via a series of command line wrapper functions around the OpenAI API. is in the first paragraph. I think that's too long for HN though, so maybe: > how to catapult your productivity via command line functions around OpenAI.

Thanks! "How to catapult your productivity" is still too linkbaity, though. The second half is good. Can you/anyone neutralize the first bit?

I asked Bing chat to summarize the article and suggest a neutral headline based on the content -

Headline: Here’s a neutral headline for the article: “Improving Programmer Productivity with Command Line Wrapper Functions around OpenAI API” .

Summary: The article at https://kadekillary.work/posts/1000x-eng/ discusses how to improve programmer productivity using command line wrapper functions around the OpenAI API. The author provides examples of functions for generating text and images, and for making code edits. The article is written by Kade Killary and was published on their website on March 29th, 2023

Re: Command line functions around OpenAI

#289

Post by dang »

fourhourstartup wrote: post #288
dang wrote: post #286

Earlier quoted context omitted.

Thanks! "How to catapult your productivity" is still too linkbaity, though. The second half is good. Can you/anyone neutralize the first bit?

I asked Bing chat to summarize the article and suggest a neutral headline based on the content - Headline: Here’s a neutral headline for the article: “Improving Programmer Productivity with Command Line Wrapper Functions around OpenAI API” . Summary: The article at https://kadekillary.work/posts/1000x-eng/ discusses how to improve programmer productivity using command line wrapper functions around the OpenAI API. The…

The first bit still doesn't seem to me to add much so I just went with the second half of zamnos's suggestion above.

Re: Command line functions around OpenAI

#290

Post by Nevermark »

wolfi008 wrote: post #281
Nevermark wrote: post #84

Earlier quoted context omitted.

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…

We should not forget that different people have different talents. That creative superstar guy may have been great at coming up with new stuff but terrible at maintaining stuff. Or at debugging some urgent prod issue under time stress on a saturday evening. You need those people too that enjoy the day-to-day maintenance to keep the house clean, or the occasional firefighting. A good team contains all those types and…

In this case, they were great maintaining stuff too. They remained available to dip into that work whenever it helped.

But as a rule, it would not have been challenging enough to keep them engaged for long. And it would have been a waste of their talents for themselves and the organization.

It wouldn't just have wasted their time directly, but wasted the opportunity for less (but still A-grade) developers from diving into a new area and maximizing its value. There was still lots of creative work to be done. These were not trivial new areas.

Post reply on HN