I now own a new house and my family is happy once again everything is finally falling into place!!

me me me

i am struggling with the same idea

Depends on the software. It's not about business acumen or profit. It's about thinking through a problem.

@@InternetOfBugs you, specifically, aren't the one I'm worried about lol.

It's not about it standing up in court, it's about getting bled dry by the fight. Even if you win, you've lost.

@@InternetOfBugs understand that can happen sometime, but it would be a very rare occurrence, especially if you’re working on things unrelated to the LOB of your employer. My agreement specifically indicates the work must be related to said business. At any rate, I wouldn’t let that hold you back, as there are many, many ways to make sure things are never found out. Large employers are unlikely to waste time and resources on it, again, unless it’s a serious direct threat.

Isn't that just rails?

@@Braindouchedotnet Maybe, I don't know much about Rails. I write mostly in C#. I know Rails is really good, but I seriously doubt it does ALL of what I just described by running a single command to install a template. Sure, you can code your brains out after you get your project set up, just like you can code your brains out in C# after you run one of the supplied dotnet templates. You're right though, something like Rails for C# is kinda what I'm thinking, but it needs more than what the basic template provides I think.

@@kdietz65 you might want to look at Django (Python on rails) and Laravel (php on rails) and in particular Laravel Forge and similar. I doubt any of them give you everything you're looking for but you can get pretty close.

@@kdietz65 Django, Laravel or Laravel Forge, spring boot.

Try taking a step back. Software development isn't a great market, because there is so much competition - so try to avoid "problems" related to that. What else do you do? Think about issues you have with your commute (or the issues you have with the process of working from home). Think about what you do to get food, or for fun, or exercise, or other non-work things. Those are the kinds of things that are more likely to be markets. But the big thing is not to sit at your desk and think about what you want to fix with software. The thing is to try to keep in the back of your mind that you're looking for problems to solve as you go about your day, and see what you notice that you hadn't thought of before.

I agree. But, in my opinion, the best way to get more knowledgeable is to build things. Most developers won't ever do that, but the ones that do tend to differentiate themselves from the pack that way.

I try to be balanced. There are things that AI is awful at (primarily things that need to be "correct" or have a right answer) and things it's helpful for, which to me is stuff where there is a huge range of potentially valid responses that vary in quality - like marketing copy or stock images.

Yeah a lot of them are doing it purely for engagement. If you can drag together an app without writing any code it will fall apart the first time something won't work as you need it too.

You're not alone. A lot of people "still find it challenging to write a software from start to finish" even after programming for years. Largely because there's not a lot of opportunity to get experience doing that when you're working for someone else as part of a team. Which is why I advocate for doing your own thing - even if that thing, itself, doesn't end up making you any money

I've seen that advice a lot, but I don't think it applies in this case. I think the "create an audience first" advice is mainly aimed at people who are trying to avoid having to spend money on development costs for ideas that aren't going to make back the money they spent on development. For a non-technical founder, the ability to pivot to a different business case often involves starting over from scratch (or nearly so), causing a lot of wasted dev time. For a technical founder, the incremental cost of pivoting is much less (in my experience), because we can understand what parts of the stack we can reuse, and what the minimum marginal effort of pivoting from one failed MVP to the closest possible MVP in the new direction. The other issue with us is, if you do the "put up a marketing site first, and don't start on development until you think you found a good niche" thing, you're likely to spend a ton of time iterating on marketing copy instead of programming, from which you won't learn anything about being a better programmer.

Really? Have you actually ever been food insecure - honestly not knowing when you were going to be able to eat next or where that food was going to come from? 'Cause I never want to feel like that, ever again.

@@InternetOfBugs if your starving making a coporation is a terrible idea since statistically speaking most small buisnesses/your startup fail due to the fundamental nature of the market economy, making a coporation is a luxury for those who can afford to fail, for the vast majority of people internationally you have two options, get a job or starve.