Hi, Iām Brayden.
A Frontend developer and freelancer. You might know me from BuildFaster.co (HTML template-selling site). If not, then itās good to meet you! š
Anywho, for the past few months, Iāve taken a break from indiehacking after dropping BuildFaster. During this break, Iāve had the time to stop, breathe, and think of new ideas. Iāve also learned new technologies like NextJS and Firebase which I can implement in future projects. š§
Well, when I started BuildFaster, I wanted to make money. Not gonna lie, š that was my goal. I didnāt think of the beginning problem thoroughly and instead jumped right to the solution. Because of that, I didnāt get onto the path I wanted originally.
This time, itās going to be different.

I want to actually take the time to brainstorm a problem and make a solution that I can scale, grow and audience with, and monetize.
So Iām opening this question up to all the developers.
No profession is perfect š , so there are always some cons about what you like to do.
It can be an issue that already exists, or something you struggle with.
I greatly appreciate your help. Thanks! š
That there is almost never a "right answer". Nearly everything you do from choosing a framework, implementing a feature, solving a problem, or writing a single line of code. Everything comes down to best guesses, experience, weighing pros/cons, etc. For people like me with decision anxiety/analysis paralysis, that can quickly lead to freezing in your tracks and not moving forward with your project.
Maybe a solution could be something along the lines of access to input from experienced professionals, access to early alpha/beta testers, or access to peer-based code reviews.
I think thatās a great idea @Harrjm! Very relevant to many developers today.
Hereās another solution I thought of. What about daily/weekly questions posted about different tech stacks or technologies and ppl vote and comment on which one is their favorite?
I think that makes for a pretty good stack of solutions. Which one would you most likely use?
You should check out https://stackshare.io/
Very useful site!
I also think your solution for peer-based code reviews or pro advice is good too. This would be a paved service I assume (for the professional advice)?
Unironically naming things š. The more you think about it, the harder it becomes.
Making implementations that are āgood enoughā. Its easy getting stuck in endless engineering because itās not perfect and thereās no one stopping you from spending infinite amount of time polishing that module or api or whatever.
Keeping to the things you know. Easier moving fast when you donāt have to learn new tech at the same time as exploring a new domain.
Choosing CSS framework.
Yes! Naming things is super hard.
Hey @Drowsy. Thanks for coming over :D
Thanks for helping me brainstorm some ideas. This is super helpful. š
files/components/variables etc. Signaling the correct intent through naming will future you (and others) very happy. Many times I think it boils down to: āI know this concept/pattern has a name but I donāt know what it is and I donāt really know how to find outā. Imagine implementing PubSub but not knowing that itās called PubSub how would you find out?
Essentially encountering a problem for the first time, your implementation will not be the best work you can produce. However when you learn more about the problem you can produce a better solution. But if you canāt measure/determine how far off your first implementation is from the ideal solution itās easy to get stuck in āI know it can be done betterā but to do it better you have to either gain new knowledge of the problem or have someone tell you how it can be improved. This typically a thing to which code reviews can help mitigate, but if youāre working alone it can be hard to find someone to do the review.
Yes! Thatās a great idea. I feel like everytime Iām gonna do frontend work I have to spend time reasearching whatās going on before starting.
Will do! :)
Thanks so much for these ideas @Drowsy! If Iāll let you know soon if I get some progress on one of these.
About 2. I don't really think there's any "technical solution" to this. It simply boils down to knowing what you want to solve and how you want to present it, and making the code easy to change: so basically, you get the interface of the class(es) right, and later can improve upon.
About a beta feature tester with upvoting - there's plenty of solutions out there, but I don't think they solve the underlying problem (encountering a problem for the first time).
Thats pretty true. @CinematicStudio. Thanks for speaking out :D
Lots of people seem to find lots of struggles, or at least voice lots of struggles, in a software development career. I for one have an opposite view; It's the most fun job and hobby I've ever had, and I've now had it for around 11 years. Sure, lots of software comes with its own kinks and things, but no matter how faulty a software is, or how hard it is to use, I still like figuring those things out. I like figuring out new programming languages, new paradigms, new platforms, it's just a hella fun thing. I mean I literally build things with my fingers! How cool is that?
In fact, the love of figuring things out is precisely why software development is such a good fit for me. I can't imagine how people who don't like solving problems would ever do this job happily. But I do, every damn day.
Love it Asko, thatās pretty true for me to. Thatās why I wanted to do this post. I love coding, but helping to solve problems that other people have would be super cool.
Solving any of these issues:
Self-hosting starts to get more and more attractive as some of these sorts of things happen to you.
Hey Mark,
Thanks for sharing out.
Do you mean making a service or platform to help vital companies stay alive and āmake a comebackā?
I think I understand what you mean. Maybe some type of community dedicated to helping with these problems? Itās a very important issue becoming more apparent. What type of solutions have you had in mind for this?
Thatās interesting, not sure if there is a proper solution other than a tool that reminds you/or them to re-read the email. What do you think? I donāt encounter this much often so I probably wouldnāt be the best person to take action on it.
Good point. What are some examples of this in your workspace? For example for mine, I use VScode a lot, which takes some memory and CPU, but I just discovered how useful Vim can be and it has a much less need for power. See where Iām going? Iād suggest finding some lower-power alternatives if possible. Thanks for giving me another nice idea to put on my list ;D
Another good point. Do you have an example of this happening? I think its a very valid point and is an issue for many developers. Thanks for sharing!
Hmm, I havent dived into AB testing too much but am somewhat familiar with it. Do you mean it will make developers obsolete? Or is it just a dumb idea all together?
Thanks Mark for sparking some ideas into my mind. This is super helpful and I greatly appreciate your help.
Dev environment setup, production environment provisioning, production logging, deployment, testing.
The list could go on and on but I think many issues about programming are not due to the act of programming itself.
Thatās very true. Thanks for being the first to say those š
Iāll add those to my list. Thanks for sharing!
My biggest struggle has been keeping up with new technologies that are made and also I sometimes find doing certain CSS animations to be difficult.
Interesting.
Would some type of personalized roadmap tool help? Or a community dedicated to those things? What would make keeping up to date with those frameworks easier?
Also, have you tried something like Animista or Anime.JS
Possibly. I'm not sure. I think having someone to help keep you focused is valuable.
No I haven't yet tried those animation libraries, but I will for future projects. Thanks!
Sounds good, let me know how it goes. I can definitely give you a few more ;)
Finding the right path to take as a Dev in 2021. Iām sure there are many people just starting out and they need a guide with everything they need to do to start out.
Any resources already out there that can help?
Hey @anthony_2!
Have you checked out roadmap.sh? Itās pretty helpful. It contains complete roadmaps for Frontend, Backend, Devops, and more.
I suggest you check it out.
Thatās a great resource. Thanks for sharing, @BraydenTW!
Youāre welcome :D
Hey,
If you build a tool thinking on behalf of me would be great. Let's say - I put in a problem, and the tool uses its own AI to solve that problem. Enough will be when the tool will return a meta description of the algorithm to solve the problem, so that I can give the meta description/instruction to any developer or even any other processor.
Andrzej,
https://pagemtr.com
Thatās pretty interesting. I, personally, donāt have any experience with AI but I think itās pretty cool. Maybe I could try making a simplified version for fun, and then evolve it into something real-world applicable.
Thanks for sharing! This is pretty useful :)