Michael Stonebraker (won the Turing award in 2014) pointed out that databases are like a Tardis. Well, that's my analogy, not his. The point is: they are alot bigger on the inside. There's a ton of stuff to tackle, and they hit every area of computer science, even though they seem kind of simple from the outside.
For personal projects, it pays better to be a little selfish write something you yourself want. Since you are the user, you will give yourself much better feedback. If you don't know the use case, you can't be the user, and that's a sign that your project has little hope of being useful. This is the same advice that Paul Graham gives for problem selection; that writers are given when they hear, "write what you know". So ask yourself, "what software do I want?" On Tuesday, June 23, 2026 at 7:33:43 AM UTC-3 Rishikesh Raj wrote: > "I want to build a low-level project for my resume. An LLM suggested > creating a database engine in Go, but I’m unsure how to approach it. Should > I pursue this project, or focus on something else? If I do build it, what > would be the practical use case?" > -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion visit https://groups.google.com/d/msgid/golang-nuts/f5a87f45-1b27-4efd-9fc0-2a9ca5f3fe6bn%40googlegroups.com.
