Some feedback if you want:

- You're overdoing it with the shadows. Simple flat design looks cleaner

- A little too many colors, that are not really aligned with each other. If you're not a designer, check out Tailwind colors and pick 1-2 you like that work complementary. Only use those and white/black/grey.

- For further reading on color picking, read up about the 60/30/10 rule in color design

- Since you've built your site with react, you could think about adding some simple animations (for example, when the books are switched on "next-book" button) by using Framer Motion. This is an opinionated thing from me.

Cool project, good start in the indie hacking community :) Keep doing cool stuff. If you wanna connect, find me on Twitter: @icebearlabs

Comments URL: https://news.ycombinator.com/item?id=37076505

Points: 1

# Comments: 0

Comments URL: https://news.ycombinator.com/item?id=36725070

Points: 1

# Comments: 0

Comments URL: https://news.ycombinator.com/item?id=36308360

Points: 1

# Comments: 0

Comments URL: https://news.ycombinator.com/item?id=36082832

Points: 1

# Comments: 0

Comments URL: https://news.ycombinator.com/item?id=36068840

Points: 2

# Comments: 0

I'm Tobias, ux software engineer by day and indie hacker by night. The last months I invested a lot of time getting the hang of chatGPT and its predecessor GPT-2/GPT-3.

Based on that knowledge and how to create the best prompts, I created a small copywriting ai tool called schreiberling.app (scribbler in english I guess). The special thing: The user isn't left alone with creating their product copy, they're asked a round of questions to get a better hang of what their product is and who it is for.

This also prompt the user to think more about their product and who their perfect customer actually is. Great for products that haven't launched yet or are not final in their product market fit.

Right now I launched my Beta v2 release, that now uses chatGPT API instead of GPT-3 (davinci), since openAI released the chatGPT api last week.

Some learning going from v1 to v2:

- People didn't know how to provide information without guided questions

- Prompt engineering for multiple languages forced me to create multiple prompts, one for each language

- I created somewhat of a prompt engine to handle things like language, but also things like "tone", to give the user more power to guide the AI to create text that actually fits their needs

- openAIs pricing is amazing. My v1 had GPT-3 calls and 100 people tried it out. I paid $1.69 that month. NOW I have the chatGPT API hooked up which costs 10x LESS than the GPT-3 endpoint. So now I'll pay around $0.17 for 100 user prompts.

- That gives me more freedom to create bigger prompts making them even better without paying myself to bankruptcy

If you have any questions or feedback, I'd love to hear it.

Comments URL: https://news.ycombinator.com/item?id=35068594

Points: 1

# Comments: 0

First thing should not be finding out what what your customers want.

First thing should be finding out IF THERE EVEN ARE CUSTOMERS for your product.

A product idea that doesn't have any market won't be successful. So find out if there are people who have a problem that can be solved, then try to solve that problem. Additionally the problem has to be annoying enough so people are willing to pay to make it go away. If you have those two, it's a great start.

You are aware, that we are on of those endangered species' when we don't change anything about climate change?

My name is Tobias and I’m excited to introduce my new Notion template: "The Software Development Health Check".

This template is a systematic approach to analyzing and improving your team's happiness, and mental health, as well as reduce stress levels.

> Why I came up with it

As a developer with 10+ years of experience, I have worked with all kinds of project managers, product owners, designers, business experts and of course other developers. While on that journey, I’ve always tried to see what works well for the dev teams and what does not. I have also done sparring and coaching for other developers and have noted what they struggle most with in their environments and with their colleagues.

All of this information, I tried to compile in this template. I have also “beta-tested” the template with other lead and senior developers to see what they had to add to my list and questions to ask. The result is a really solid template to find issues within your team and how to improve them.

In the end, I wanted to create a template, that helps team leads, project managers and lead devs to create a more fun working environment.

> Here's what you'll find inside

- A structured way to approach your teams current state and what questions to ask - Multiple tests you can take, to find out what’s going right, what could be improved and what you can add to your process - Suggestions on what to do to get the team to a better place

I built this template with my experience of 10+ years in large development teams. Added to that are dozens of discussions I had with other lead or senior developers to include their viewpoint as well.

As I continue to improve the template over time, I will release new free templates that you can add to this base template to add even more functionality. Stay up to date by following me either on Twitter [1] or on Gumroad [2]. I’ll message you when I have new freebies!

I would love to hear your feedback on it!

Thank you

Links:

[1]: https://twitter.com/icebearlabs [2]: https://icebearlabs.gumroad.com/

Edit: Read the disclaimer myself. She seems to defent seeing a snow leopard, as she also has a picture of its paw up in the same collection. Make of that, as you will.

So, I go deeper into this in the actual template, but you're not supposed to check ALL of the boxes in ALL scenarios. This is not meant as a test, but rather a checklist, hence I changed the name from test to checklist after the first draft.

So for some things, your team, your company etc. will differ from me and my questions. Which is absolutely fine! This doesn't want to be a dogma and different things work for different people. I HAVE talked to more enterprisey devs, but have also worked myself in both environments. I hope both kinds of people can benefit from it in the end :)

I used this article as a test: https://www.saarbruecker-zeitung.de/saarland/landespolitik/s...

What was often missing, was how the developing process should be handled, where information should be saved and how the team should work, on a day to day basis. Working with different teams you could always find things that did not go great in those categories.

This product is my attempt to give you a tool to find those problems and fix them for your team.

As you can see it's free to download and use and will stay that way. Would love to hear everyone's feedback and what might be missing from it. It was created from my personal experience, as well as multiple feedback rounds with other senior developers and agile team members.

Comments URL: https://news.ycombinator.com/item?id=33731092

Points: 3

# Comments: 2