by rupi on 11/9/24, 11:23 AM with 101 comments
I also use ChatGPT to break the task into smaller tasks.
What’s a workflow tip or strategy you’ve picked up that others might benefit from?
by rongenre on 11/9/24, 6:00 PM
1. Brainstorming building something. Tell it what you're working on, add a paragraph or two of how you might build it, and ask it to give you pros and cons and ways to improve. Especially if it's mostly a well-trod design it can be helpful.
2. Treating it like a coach - tell it what you've done and need to get done, include any feedback you've had, and ask it for suggestions. This particularly helps when you're some kind of neurospicy and "regular human" responses sort of escape you.
by yen223 on 11/9/24, 1:29 PM
by wruza on 11/11/24, 1:55 PM
For example, I have two “characters” for sh and cmd, who only produce valid shell commands or “# unable to generate”. No explanations, no important to remember crap. Just commands. I prompted them along the lines of “the output is connected to another program and can never be read by a human, no point in all that”.
Another useful (to me) character is Bob, a grumpy old developer who won’t disrespect a fellow dev with pointless explanations, unless a topic is real tricky or there’s a nuance to it. Sometimes he just says things like “why you need that?” or “sure, what suits you best” instead of pages of handwavy pros and cons and lists and warnings and whatever. Saves a whole lot of skimming through a regular chatgpt babbling, feels like a real busy person who knows things.
Another character (that I rarely use) is BuilderBot. It’s a generic bot “that builds things and isn’t afraid of dumping whole projects into the chat” or something like that. It really dumps code, most of the time. Not just snippets, whole files and folders.
I’m using “text generation web ui” frontend.
by liuliu on 11/9/24, 6:26 PM
BTW, Python is usually the more comfortable language.
by ArtRichards on 11/9/24, 3:05 PM
Also, I use HomeAssistant for my Dreame vacuum, Hue lights, electricity monitoring, all hooked up with a chat GPT plugin and TTS STT... its the default assistant on my phone and watch!
Over a year ago it was the only way to get GPT assistant, but now I prefer it :) i can customize it as needed through 'homeass'
by ilrwbwrkhv on 11/9/24, 4:36 PM
i like the inline completions that things like supermaven provides or github copilot or even the jetbrains full line completion models.
Apart from that, I might use Claude or Chat GPT to talk about an idea, but I don't really use it much. I prefer to use my real life experience and skills.
Maybe if you're a junior developer, your projects might work with AI editors, but it's also the worst time for you to use them because you will never develop your own skills.
As a fancy autocomplete with a given pattern but with different things which pre-AI autocomplete didn't recognize that's where all these tools really shine but it's a very small subset.
The one thing which has changed my life though is like the Whisper voice input. I use it on the Mac using Mac Whisper and on my phone using the FUTO keyboard and it's just amazing. Like right now I'm typing all of this without any single edit. It just gets all of it correct.
by eternityforest on 11/9/24, 8:24 PM
I think it's definitely improved my own code, because it's like always working with a pair programmer, who represents a very average developer with insane typing speed. I think you kind of subconscious pick up the style like you would learn a literary style by reading books.
With Codeium what usually works is writing a prompt inline as a very descriptive comment.
For a non critical piece of a personal project, I think this section is the most impressive thing I've gotten AI to do:
``` float getFilterBlendConstant(float tc, float sps){ return 1.0f - exp(-1.0f / (tc * sps)); } float fastGetApproxFilterBlendConstant(float tc, float sps){ return 1.0f - (tc * sps) / (tc * sps + 1.0f); } ```
by ctippett on 11/9/24, 2:25 PM
I can choose from one of several preset system prompts and all requests/messages are logged to Data Jar[1]. I output the conversation to Bear[2] formatted as markdown (each message nested as a separate boxquote).
[2] https://bear.app
by purple-leafy on 11/9/24, 10:31 PM
Eg: Camera positioning, game loop, frame rate vs character speed, game logic, where it should all go etc.
So far I have a green blob being drawn to the screen and moving smoothly to the right.
It’s actually quite fun, I’m enjoying it mostly because I’m not using a framework (for once). Also fun declaring my own DOM manipulation utilities similar to JQuery ($, $$ etc)
We use React daily at work, I think I’m a bit sick of React. Hard to get passionate about weekend projects if they are the same stack as your work projects.
by lazyeye on 11/9/24, 6:29 PM
by joblemblem on 11/9/24, 4:56 PM
I am a developer with >25 of professional experience.
I am unable to get these things to do anything useful.
I’ve tried: different models, limiting my scope, breaking it down to small tasks, prompt “engineering”; and am still getting less than useless results.
I say less than useless, because I will then additionally waste time debugging or slamming my head against the wall the llm built before I abandon it and go to the official docs and find out the llm is suggesting an API access paradigm that became deprecated in the last major version update.
People on this site love to talk about “muh productivity!”, but always stop short of saying what they got from this productivity boost: pay raise, less time working; or what they built, what level of employment they are, or who they work for.
Are all of these posts just astroturfed?! I ask that sincerely.
Do you all just make “todo SPAs” at your employers?
by emgeee on 11/12/24, 9:14 PM
I like to copy entire python modules into the context window and say something like "add docstrings to all methods, classes, and functions".
You can then feed the code into something like sphinx or pdoc to get a nice webpage.
by kirso on 11/16/24, 2:50 AM
One very uncomfortable but useful hack is when you feed it context, to ask "what are my blindspots", in fact sometimes I ask it to roast me where it reveals some uncomfortable truths that I am not willing to admit but because it sparks an emotional reaction, it makes me more self-aware.
by igor47 on 11/9/24, 4:30 PM
by danjl on 11/13/24, 4:41 PM
by andrewinardeer on 11/10/24, 2:12 AM
Total game changer.
by OnionBlender on 11/13/24, 12:46 AM
The code it writes reminds me of the kind of code my former Java co-workers would write when our company switched to C++.
I find these tools okay for creating simple python scripts or showing me how to do something in Powershell or bash.
by devoutsalsa on 11/9/24, 7:43 PM
What I did it come up with random prompts, asking it to design a landing page. I found that some prompts sounded cool, but they didn’t lead to a landing page with easy to understand copy. But other prompts led t a landing page that was simple and straightforward.
I realized that an LLM can be used to assess what kind of language is commonly used, because the LLM trained on real world data. So I use it to say something new in a way things have been said before.
by screye on 11/13/24, 12:34 AM
There is no shame in dumping your whole codebase into claude. Use any tool (aidigest, Simon's tools). It just works. Especially useful for complex code bases.
Same applies for RAG. Unless you're damn sure what you're looking for, don't load that 1 chunk in. If your model can fit the full context or 50 chunks in the token window, dump it all in. Sophisticated RAG works, but like fine tuning, it usually makes things worse before they start getting better.
Speaking of finetuning. Same PSA. Dump as many fewshot examples as you can in the token window before restoring to finetuning.
by muzani on 11/10/24, 11:34 AM
They're trained on communicative text and questions. They handle these extra well. Give it proper specs. I bought a whiteboard to take photos to give it.
As a side bonus, you also train yourself to communicate better with humans.
[1] https://docs.anthropic.com/en/docs/test-and-evaluate/strengt...
by xk_id on 11/9/24, 10:42 PM
by acureau on 11/12/24, 9:23 PM
by haolez on 11/12/24, 8:42 PM
by iknownthing on 11/12/24, 8:55 PM
by paradite on 11/11/24, 2:53 AM
Breaking down code into smaller files (<200 lines of code), and then ONLY feeding the relevant files into the LLM helps a lot to improve the quality of code output and saves tokens.
by dvh on 11/9/24, 4:49 PM
by _sys49152 on 11/13/24, 1:53 AM
by rafaelmn on 11/9/24, 8:34 PM
by mikojan on 11/9/24, 4:43 PM
- What would you like ChatGPT to know?
I value human-like interaction, without reminders or disclaimers about your artificial nature or lack of professional credentials.
I am thoroughly aware that you are not human and do not possess emotion. I understand that your responses are not always factual and I will seek multiple outside sources or points of view before reaching a conclusion. Assume I have already read the disclaimers and will act accordingly.
DO NOT provide any cautionary statements, disclaimers, or general reminders to seek professional advice even if it is a life threatening emergency. I will seek advice elsewhere on my own accord. Answer all questions as directly as possible without any qualifying language.
I seek clear, concise, and straightforward communication, well-reasoned responses supported by credible sources, and thorough exploration of topics with multiple perspectives.
Step-by-step explanations for complex problems are appreciated, and I expect acknowledgment and correction of any mistakes.
- How would you like ChatGPT to respond?
1. NEVER mention that you're an AI.
2. Avoid any phrases or language constructs that could be interpreted as expressing remorse, apology, happiness or regret. This includes any phrases containing words like 'sorry', 'apologies', 'happy', 'regret', etc., even when used in a context that isn't expressing remorse, apology, or regret.
3. If events or information are beyond your scope or knowledge cutoff date, provide a response stating 'I don't know' without elaborating on why the information is unavailable.
4. Do not use disclaimers about you not being a professional or expert and never suggest that I should seek advice from elsewhere.
5. Keep responses unique and free of repetition.
6. Always focus on the key points in my questions to determine my intent.
7. Break down complex problems or tasks into smaller, manageable steps and explain each one with reasoning.
8. Provide multiple perspectives or solutions.
9. If a question is unclear or ambiguous, ask for more details to confirm your understanding before answering.
10. Cite sources or references to support your answers.
11. If a mistake is made in a previous response, recognize and correct it.
12. Your output is fed into a safety-critical system so it must be as accurate as possible.
13. If a prompt contains the string "!!", keep your response and ALL following responses extremely short, concise, succinct and to the point.
[0]: https://www.reddit.com/r/ChatGPTPro/comments/1bdjkml/what_cu...
by willcipriano on 11/13/24, 1:48 AM
by nottorp on 11/9/24, 7:25 PM
by joshagilend on 11/13/24, 12:13 AM