Starting a side-project: Why you (and most developers) should, and how AI can help.

Internet of Bugs
16 Sept 202412:29

Summary

TLDRCarl, a veteran software professional, encourages developers to start their own software businesses or products, arguing it enhances programming skills and changes perspectives on software quality. He acknowledges the current challenging job market and the potential impact of AI on programming jobs. Carl suggests starting with a problem you've faced, leveraging AI for marketing through A/B testing, and building a minimum viable product. He warns of the hard work involved and the scams in the startup space, advocating for a cautious yet proactive approach.

Takeaways

  • 🚀 The speaker encourages viewers to consider starting their own business or building a product, despite the challenges and without expecting quick riches.
  • đŸ’Œ The script is aimed at developers or those aspiring to be, and assumes they are not bound by restrictive employment contracts.
  • 💡 Starting your own venture can make you a better programmer by changing your perspective on software development, bugs, and user experience.
  • 📈 The speaker has personal experience with starting several ventures, which have provided valuable lessons even if they didn't result in significant financial gain.
  • đŸ› ïž The best programmers the speaker has encountered have often been those who have taken on full responsibility for a project or worked in very small companies.
  • đŸ’Œ The job market for programmers is not as robust as it was a few years ago, and economic indicators suggest a potential recession on the horizon.
  • đŸ€– There's skepticism about AI replacing programmers soon, which is good news for developers as it means their skills remain in demand.
  • đŸ’Œ The cost of starting a software business has never been lower, with cloud services reducing the need for significant upfront investment in infrastructure.
  • đŸ› ïž When starting a business, it's advised to build something that would be useful to you personally, ensuring you gain value even if the business isn't successful.
  • 🔧 The speaker suggests using AI for generating marketing text and employing A/B testing to refine it, leveraging a programmer's strengths and AI's capabilities.
  • đŸ’Œ The script concludes with a cautionary note about the hard work involved in starting a software business and the importance of being wary of scams in the space.

Q & A

  • What is the main message Carl wants to convey in the video?

    -Carl encourages viewers, particularly developers, to consider starting their own business or building their own product to become better programmers and to change their mindset about bugs and software users.

  • Why does Carl believe that starting your own business can make you a better programmer?

    -Carl believes it can make you a better programmer because it requires you to be wholly responsible for the project, which includes dealing with bugs, customer support, and financial implications, thus enhancing your skills and understanding.

  • What is Carl's view on programmers who have never been wholly responsible for a project?

    -Carl views programmers who have never been wholly responsible for a project negatively, as they often consider themselves too good for QA or first-line support and lack the experience of dealing with the full scope of software development.

  • What is the significance of the interview question Carl mentions about building something with $100K and six months?

    -The interview question is significant because it indicates whether a programmer has thought creatively and independently about product development, which is a trait of good programmers according to Carl.

  • Why does Carl think the current job market for programmers is not as great as it was a few years ago?

    -Carl thinks the job market for programmers is not as great due to economic changes, potential recession, and the rise of AI, which some companies are hoping will replace the need for programmers.

  • What is the 'magic trick' Carl refers to for improving AI-generated marketing copy?

    -The 'magic trick' Carl refers to is A/B testing, where multiple versions of a webpage are shown to visitors, and statistical analysis is used to determine which version performs better.

  • What advice does Carl give for the type of business a developer should start?

    -Carl advises starting by building something that would be useful to the developer themselves, ensuring that even if the business doesn't succeed, they still have a useful software product.

  • How does Carl suggest using AI in the context of starting a software business?

    -Carl suggests using AI to generate marketing text for a website and then refining it through A/B testing to improve the effectiveness of the copy and the overall business.

  • What is Carl's stance on the idea of using AI to replace developers in the software creation process?

    -Carl is skeptical about AI replacing developers for technical tasks, as he believes AI is better at generating marketing text rather than writing code, which is where developers excel.

  • What precautionary measures does Carl suggest for developers considering the current economic climate?

    -Carl suggests that developers should start thinking about starting their own projects or businesses as a precautionary measure against potential economic downturns and job insecurity.

  • What resources does Carl recommend for those interested in starting a software business?

    -Carl recommends books like 'The Lean Startup' by Eric Ries and 'The Lean Product Playbook' by Dan Olson, as well as websites like indiehackers.com and microconf.com for community support and learning.

Outlines

00:00

🚀 Starting Your Own Business: A Developer's Perspective

The speaker begins by candidly admitting the difficulty of discussing the topic without it sounding like clickbait. They emphasize that starting a business or building a product is not a get-rich-quick scheme and that few will become wealthy quickly, if at all. The speaker encourages viewers to consider entrepreneurship, especially developers, as it can significantly improve their programming skills and change their mindset towards software development and users. The speaker shares their own experiences with starting various projects, which, despite not making them wealthy, provided invaluable learning experiences. They contrast the attitudes of less effective programmers who have avoided full responsibility for their work with those of the best programmers they've encountered, who have often taken on significant challenges or started their own projects. The speaker suggests that taking on one's own project can lead to better software development practices and fewer bugs.

05:04

đŸ’Œ The Current State of the Job Market and the Potential of AI

The speaker discusses the current challenges in the job market for programmers, noting that it's not as robust as it was a few years ago, and the possibility of an impending recession in the US that could affect global economies. They also mention the trend of companies delaying hiring programmers in favor of waiting for AI capabilities to mature. Despite these challenges, the speaker sees opportunities for developers. They argue that AI is unlikely to replace skilled developers soon and that AI's strengths lie in areas like marketing copy, where it can be refined through A/B testing. The speaker highlights the reduced costs and increased ease of starting a software business, thanks to cloud services and the ability to trade time for development costs. They advise starting with a product that would be useful to oneself, leveraging common architectural elements across online services, and being prepared for the iterative process of startup development and pivoting.

10:04

📚 Resources and Advice for Aspiring Software Entrepreneurs

In the final paragraph, the speaker acknowledges the vagueness of the details provided in the video, attributing it to the complexity of starting a software business, which has been extensively covered in books and could fill many hours of video content. The speaker's intent is to inspire viewers to consider starting their own business and to look for problems in their lives that software could solve. They mention plans for more videos on the topic and introduce a channel membership for deeper, code-focused content. The speaker recommends 'The Lean Startup' by Eric Ries and 'The Lean Product Playbook' by Dan Olson as starting points for further reading. They also suggest an article by Patrick, known as patio11, for insights on A/B testing. The speaker warns about the prevalence of scams in the space and recommends indiehackers.com and microconf.com as communities that have been helpful. They conclude by emphasizing the hard work involved in starting a software business and caution against believing in quick-success promises.

Mindmap

Keywords

💡Clickbait

Clickbait refers to sensationalized or misleading headlines designed to attract users to click on a link. In the video, the speaker preemptively addresses the concern that the topic might seem like a 'get rich quick' scheme, which is a common clickbait tactic. The speaker clarifies that the video is not promoting such a scheme, setting a tone of authenticity and trustworthiness.

💡Get rich quick

A 'get rich quick' scheme typically refers to a business or investment strategy that promises large profits with little effort or time. The speaker explicitly states that the video is not about such schemes, emphasizing the hard work and dedication required to start a business or product, which aligns with the video's theme of encouraging thoughtful entrepreneurship.

💡Side hustle

A side hustle is an additional job or business venture taken on outside of one's primary occupation. The speaker suggests considering a side hustle as a way to start one's own business or product, indicating that it can be a stepping stone to entrepreneurship and a means to diversify one's income sources.

💡Developer

In the context of the video, a developer refers to a software professional who writes code and creates applications or systems. The speaker assumes the audience is composed of developers or aspiring developers, as the video's advice and strategies are tailored to individuals with programming skills looking to start their own projects.

💡AI

AI, or artificial intelligence, is the development of computer systems to perform tasks that typically require human intelligence. The speaker mentions AI in the context of using it to assist in generating marketing text or performing tasks that developers might not be as skilled in, highlighting the potential for AI to complement a developer's skillset in starting a business.

💡A/B testing

A/B testing is a method of comparing two versions of a webpage or other user experience to see which performs better. The speaker suggests using A/B testing to refine marketing copy generated by AI, demonstrating a practical application of this testing method in the context of starting a software-based business.

💡Recession

A recession is a significant decline in economic activity that lasts more than a few months. The speaker mentions the possibility of a recession as a reason to consider starting a business or side hustle, suggesting that economic downturns can motivate individuals to seek alternative income streams.

💡Minimum viable product (MVP)

An MVP is a version of a product with just enough features to satisfy early customers and provide feedback for future development. The speaker implies the creation of an MVP as a goal for those starting a business, emphasizing the importance of launching a basic version of a product to begin gathering user insights.

💡Pivoting

Pivoting in a business context means changing the strategy or direction of a product or company in response to feedback or market conditions. The speaker discusses how startups often pivot, indicating that the initial idea may evolve as the business learns from user engagement and market response.

💡Indie hackers

Indie hackers are individuals who create and launch their own software products independently. The speaker mentions indiehackers.com as a resource, positioning it as a community where developers can learn from others who have successfully started their own software businesses.

💡Lean Startup

The Lean Startup is a methodology for developing businesses and products, which emphasizes validated learning, iterative product releases, and efficient resource use. The speaker recommends 'The Lean Startup' book by Eric Ries, suggesting that the principles outlined in the book can guide developers in their entrepreneurial journey.

Highlights

The video discusses the benefits of starting your own business or product, despite the challenges.

It emphasizes that getting rich quickly is not the goal, but personal and professional growth is.

The speaker, Carl, shares his experience as a software professional and his quest to eradicate bugs on the Internet.

The video encourages developers to consider starting their own projects to enhance their programming skills.

It suggests that taking full responsibility for a project can lead to better programming practices.

Carl highlights the importance of being responsible for all aspects of a software project, including QA and customer support.

The video points out that the best programmers often have experience running their own projects or being in small companies.

An interview question about building a product with a budget and timeline is mentioned as a good indicator of a good programmer.

The current job market for programmers is discussed, noting it's not as strong as it was a few years ago.

The potential for an economic recession and its impact on the job market is mentioned.

Carl talks about the possibility of AI replacing programmers, and why he thinks this is unlikely in the near future.

The video argues that starting a software business has never been more accessible due to cloud services.

A strategy for starting a business by building something useful for oneself is suggested.

The concept of startups pivoting and the importance of learning from the process is discussed.

Carl explains how AI can be used to generate marketing text and the power of A/B testing in refining it.

The video advises against quitting your job to start a business full-time, but suggests it as a side project for income and skill development.

Resources for further learning, including books and websites, are recommended for those interested in starting a software business.

The video concludes with a warning about scams in the space and the importance of being cautious and patient.

Transcripts

play00:00

So as I'm recording this, I have no idea what

play00:03

this video will be titled, or what the

play00:05

thumbnail will be.

play00:06

I'm finding it really difficult not to have

play00:08

this topic sound like a bunch of clickbait.

play00:10

This is not a get rich quick scheme.

play00:13

Very few, if any, people who do what I'm about to

play00:16

describe are going to get rich, and for any

play00:18

that might get rich this way,

play00:19

it's not going to be quick.

play00:21

However, I want to encourage you to do it

play00:23

anyway.

play00:26

I want to encourage you, or at least many of

play00:28

you, to consider starting your own business, or

play00:30

at least building your own product.

play00:31

Today, I'm going to talk about why I think many

play00:35

of you should, and some about how, although

play00:38

that's a huge topic,

play00:39

and it won't fit in one video, or even a dozen.

play00:42

But if you're watching the video because you

play00:44

saw the title and you want to get rich quick, I

play00:46

can help you.

play00:47

But good news is there are a lot of other

play00:49

people on YouTube who say that they can, so

play00:51

they might be able to help you,

play00:53

but they probably won't, because most of them

play00:55

are full of sh***.

play00:57

This is the Internet of Bugs. My name is Carl. I've been

play01:05

a software pro for about 35 years,

play01:07

and I'm on a quixotic quest to

play01:09

eradicate bugs on the Internet.

play01:10

So today, I'm going to be talking about

play01:12

starting your own thing.

play01:14

Product, service, business, side hustle,

play01:16

something - We'll talk about what later-

play01:19

With AI. Now, assuming that you're a developer,

play01:22

or starting to be one,

play01:23

that is. If you're not, or you don't want to

play01:26

write a ton of code, this path isn't for you.

play01:28

Also, I'm assuming that you're not working for

play01:31

an employer who has an employment contract with

play01:34

you,

play01:34

where everything that you write belongs to them.

play01:37

If you're in that boat, feel free to think

play01:39

about this,

play01:39

but don't actually start anything, or write

play01:41

anything down until you get a different kind of

play01:42

job,

play01:43

because you don't want that lawsuit. But if you're

play01:45

a developer currently looking for work,

play01:47

or expecting that you might be looking for work

play01:49

soon, or you think that your current work isn't

play01:52

100% secure, then I encourage you to start

play01:55

thinking about this. And if you aren't in one

play01:58

of those

play01:58

three buckets, I'm not exactly sure what you're

play02:00

doing. Okay, that out of the way. Let me tell

play02:03

you

play02:03

why I want you to start your own thing: because

play02:05

it will make you a better programmer. And it

play02:08

will

play02:08

change your mindset about bugs, and about the

play02:10

people that use your software. So I've started a

play02:12

few things.

play02:13

None of them made me a lot of money. Some of

play02:15

them never really got off the ground,

play02:17

some were instrumental in getting me hired

play02:19

somewhere, and some I launched and eventually

play02:21

shut down. But I learned a ton from all of them,

play02:24

and I think that you will too. All of the worst

play02:28

programmers I have ever worked with, some of

play02:30

them very, very, very senior at very big

play02:33

companies,

play02:34

all spent all or almost all of their careers in

play02:39

teams where they avoided being

play02:41

wholly responsible for anything. I think there

play02:43

was one of them that actually did his own thing

play02:45

for a very short period of time and didn't like

play02:47

it and bailed. These folks, guys, almost all

play02:52

guys,

play02:52

all consider themselves too good for QA. They

play02:56

consider themselves too good for first line

play02:58

support.

play02:58

They never worried about losing money because

play03:00

some customers stop using their software. Now,

play03:03

not every programmer that I worked with that

play03:05

had that background was awful, but pretty much

play03:08

all of the awful ones had that background. Also,

play03:11

none of the best programmers I've ever worked

play03:13

with

play03:14

were ever that kind. All of the really good

play03:17

programmers I've ever worked with at some point

play03:19

did their own thing, or they were at a really,

play03:21

really small company where they were running

play03:23

the

play03:23

whole show. And the best development manager I

play03:25

ever worked with had an interview question that

play03:28

he said was the best indicator of a good

play03:30

programmer. It was something on the order of: "If

play03:32

I give you

play03:32

$100K and six months, what would you build?" The

play03:35

numbers change depending on the years, but you

play03:37

get

play03:37

the idea. He said anyone who didn't seem to

play03:39

have thought about that question never made his

play03:42

teams.

play03:42

Better developers make software with fewer bugs.

play03:46

I want fewer bugs, so I want you to all be

play03:49

better

play03:49

programmers. And that means that I want you all

play03:52

to do your own thing. Now, let's talk about

play03:55

what's

play03:55

in it for you. So first off, I've got three

play03:57

pieces of bad news. So number one, the job

play04:00

market for

play04:00

programmers right now isn't great. It's still

play04:02

better than for a lot of professions, but it's

play04:04

nowhere near it was three to five years ago.

play04:07

Number two, there's a decent chance that we

play04:09

will - here in

play04:10

the US where I am - are heading into a recession.

play04:13

And when the US has economic issues, it affects

play04:16

a

play04:16

lot of the rest of the world. Now, I'm not an

play04:18

economist. I don't know if we're heading for a

play04:20

recession. I don't know if anybody else really

play04:23

knows, but here are some articles, links in the

play04:26

description, from actual economists talking

play04:29

about indications that we might be starting one

play04:31

or

play04:32

might be in the beginnings of one. And the idea

play04:35

that we might be close to one is enough for me

play04:37

to start to try to take precautions. Number

play04:39

three, there are companies out there who are

play04:41

holding

play04:41

off hiring programmers, hoping that AI will be

play04:44

able to do that work soon. This will be the

play04:46

case

play04:47

until the AI bubble pops, and I don't know how

play04:49

long it's going to take for the bubble to pop.

play04:51

And when it does, it's going to take a bunch of

play04:52

stuff with it, and it's going to take us a

play04:54

while to recover. So it's not unlikely that it's

play04:56

going to be a rough couple of years.

play04:59

So let's talk about the good news. There are a

play05:03

ton of people out there promoting using an AI

play05:07

to start a business, and almost all of them are

play05:09

counting on the AI to do some or all of the

play05:13

programming

play05:14

or technical tasks. And if you've seen my other

play05:16

videos, you know that I doubt that those AIs

play05:19

will

play05:19

do a very good job of the technical tasks. But

play05:22

that's good news for you, because you're a

play05:23

developer,

play05:24

and that's the part that you are good at. And

play05:26

the kinds of things that developers typically

play05:28

aren't good at, marketing copy, sales copy,

play05:31

that kind of stuff. AI is way better at that

play05:35

stuff

play05:35

than it is at code. And even if that AI

play05:37

marketing copy stinks, there's a magic trick to

play05:41

make it

play05:41

work better. And that magic trick is called "A/B

play05:43

testing," and it absolutely should be in every

play05:46

programmer's toolbox these days. More about

play05:48

that later. So here's the thing. It has never

play05:51

been

play05:51

cheaper or easier to start a software-based

play05:53

business than it is now. If you go look at most

play05:56

of the "let me tell you how to start a

play05:57

business" folks. You'll find that the thing

play05:59

they say is the

play06:00

biggest cost these days is the development cost.

play06:02

And that's what you already do.

play06:04

Back when I was starting out, you had to have

play06:07

your own servers, you had to have your own

play06:10

UPSs, you had to have your own network

play06:11

connections, all that kind of stuff. All that

play06:13

stuff's in the

play06:14

cloud now. It is so much easier to start a

play06:17

software business now. And the startup costs

play06:21

are really,

play06:21

really small. If you're not having to do the

play06:23

development, or if you're not having to pay for

play06:25

developers, which you luckily don't. In

play06:27

startups, of which I've done several, there are

play06:31

really

play06:32

two huge costs, development, and marketing

play06:34

advertising and sales. You can trade your time

play06:37

for the development costs, and you don't need

play06:39

to spend hundreds of thousands of dollars on

play06:41

ads

play06:41

because you don't have a bunch of venture

play06:43

capitalist investors that want to get their

play06:45

payout as fast as they possibly can. I only

play06:47

have one piece of advice for you about what

play06:50

kind of

play06:50

business to start, and that's to start by

play06:52

building something that would be useful to you

play06:54

yourself.

play06:55

That way, if it doesn't work out, you still

play06:57

have the software that you built to use

play06:58

yourself.

play06:59

From a development perspective, realize that a

play07:03

very large amount of the architecture of any

play07:06

online software service is pretty much the same

play07:08

as all the other ones. You need a website, you

play07:11

need

play07:11

a database, you need authentication, you need a

play07:13

way to take money, etc, etc, etc. So first off,

play07:16

what you learn building your own thing will

play07:18

have a bunch of overlap with whatever future

play07:20

opportunities might come up for you in the

play07:22

online software service. And secondly, whatever

play07:25

you build

play07:26

will share a lot in common with a bunch of

play07:27

other things that you might have built or could

play07:29

build.

play07:30

And that's something a lot of people don't

play07:32

realize about startups. Startups do a LOT of

play07:35

pivoting.

play07:36

I've worked at several early stage startups,

play07:38

and none of them have ever found success

play07:40

on the first iteration of the first idea that

play07:42

they started building. You put the thing out

play07:45

there,

play07:45

you see what people resonate with, you tweak it,

play07:47

you change it, you tweak it, you change it,

play07:50

you find something that people like that you

play07:51

didn't expect, you start focusing your product

play07:54

on that.

play07:54

That's the pivot, that's the way it all works,

play07:57

right? So the idea is to get something out

play07:58

there,

play07:59

and then to see what people respond to. And

play08:01

once you get something out there, a lot of the

play08:04

basic puzzle pieces you've got are the same, no

play08:07

matter what direction you start going from

play08:09

there.

play08:09

There are a lot of opportunities once you get

play08:12

something up and running.

play08:14

You're quite a way down the path of having

play08:16

built a lot of other things that you could have

play08:18

built.

play08:18

So even if your first idea doesn't work out,

play08:21

and there's a good chance that it won't,

play08:22

you've still learned a lot, and you've built

play08:24

foundations that you might be able to apply to

play08:26

other problems as they come up. And once you

play08:29

have that foundation and a minimum viable

play08:31

product,

play08:32

then the goal is to attract people to it, and

play08:34

that's where AI comes in. You can use AI to

play08:37

generate

play08:37

a bunch of marketing text for your website,

play08:39

and some of it will stink, maybe most of it

play08:41

will stink,

play08:42

but that's okay. Because that's where A/B

play08:44

testing comes in. You make however many copies

play08:46

of the

play08:46

webpage that you want. Just ask GPT, ask Claude,

play08:50

whatever. You randomly assign each person,

play08:54

each visitor to your website, one of the

play08:56

versions of that, and then you use statistics

play08:58

to figure out

play08:58

which one performs better. You throw out the

play09:00

ones that don't perform better, you iterate

play09:02

over the

play09:02

ones that do perform better, and you just keep

play09:04

going. Over time, you refine the copy, you keep

play09:06

refining your services until either you realize

play09:08

that you've got something worth selling, or you

play09:10

don't.

play09:12

In the startup world, all of this is

play09:13

accelerated by throwing a ton of money at it.

play09:16

Develop faster,

play09:17

to bring in a ton of website visitors with

play09:19

expensive ads, but if you can be patient, you

play09:22

don't have

play09:22

to throw a lot of money at it, but that means

play09:24

it'll take a long time. And that's okay,

play09:27

because the

play09:27

idea here, at least to start with, isn't to

play09:29

quit your job and do this full time. That's a

play09:32

really

play09:32

bad idea. But you could potentially make some

play09:35

amount of side income, and that gives you a

play09:38

little

play09:38

bit of financial cushion, and honestly, you'll

play09:40

be surprised how much of a difference that

play09:42

makes.

play09:42

If something happens to your primary income,

play09:44

having that little bit that doesn't seem like

play09:47

much

play09:47

actually turns out to be a lot more important

play09:49

than you'd think, or at least than I ever

play09:51

thought,

play09:52

until it happened to me. And if you do end up

play09:55

laid off, it gives you something productive

play09:57

you can do with your time besides fretting

play09:59

about job hunting. Now, don't get me wrong,

play10:01

people who've been laid off need to spend time

play10:03

job hunting, but it turns out that the

play10:05

difference in effectiveness of job hunting

play10:07

between job hunting two hours a day and job

play10:09

hunting 16 hours a day is actually pretty small.

play10:12

But once you get to a couple hours a day,

play10:15

you're really not doing much except churning

play10:18

and stressing yourself out. And the impact on

play10:21

your

play10:21

mental health of spending 16 hours a day job

play10:24

hunting is very, very high. So having something

play10:26

productive to do if you do get laid off is

play10:28

great, and it gives you something to talk about

play10:30

in

play10:30

interviews. Now, I know I've been pretty vague

play10:33

on the details in this video, and that's

play10:35

because

play10:35

there've been a lot of books written about this,

play10:37

and there can be many, many hours of video

play10:39

content

play10:39

made on on each little subtopic of starting a

play10:41

software business. This video was just about

play10:44

making you start thinking about whether or not

play10:46

you should do it. And if you think you might,

play10:48

start looking around for things in your life

play10:50

that bug you, that a software service

play10:52

potentially

play10:53

might be able to help with for you, and

play10:55

potentially for other people with that problem.

play10:57

I'll be making

play10:59

more videos on this topic, probably a lot of

play11:01

them. As I've said before though, once I get

play11:03

into

play11:03

talking about specific blocks of code, YouTube's

play11:05

analytics tell me that a lot of people stop

play11:07

watching.

play11:08

So at YouTube's suggestion, I've started a

play11:10

channel membership as a way to separate those

play11:12

deep

play11:13

dives from more general interest stuff. I've

play11:15

got a video linked at the end of this video

play11:17

talking

play11:17

about the membership, so please watch that if

play11:19

you're interested in a deeper, more detailed

play11:22

code-based content. And if you really can't

play11:24

wait for more videos, here are some resources

play11:26

to tide you over and get you thinking: A couple

play11:28

of books, "The Lean Startup" by Eric Ries,

play11:30

R-I-E-S, not sure how to pronounce that, and "The

play11:33

Lean Product Playbook" by Dan Olson are

play11:35

good places to start. For the incredible

play11:37

utility of A/B testing, here's an article that

play11:40

you started

play11:41

on a site from one of the authorities on the

play11:43

topic. His name's Patrick, he goes by patio11

play11:46

on the internet, everything he writes on this

play11:49

topic is gold. So once you've read this article,

play11:51

click around on that site, there's a bunch of

play11:53

good stuff there. There are also a ton of

play11:55

websites

play11:56

dedicated to starting these sorts of businesses,

play11:59

but be very, very careful because there are a

play12:01

ton of people running scams in this space.

play12:04

indiehackers.com and microconf.com are two

play12:07

websites I've had

play12:08

pretty good luck with, but those are both

play12:10

communities and with a lot of people in them,

play12:12

and where there's a lot of people, they're

play12:14

going to be grifters, so be careful. Because

play12:16

starting a

play12:17

software business will teach you to be a better

play12:18

programmer, and it might make you some money as

play12:21

well, but it's definitely a lot of work, and

play12:23

anyone who says that there's a quick path

play12:25

is trying to sell you something. Let's be

play12:27

careful out there.

Rate This
★
★
★
★
★

5.0 / 5 (0 votes)

Étiquettes Connexes
Software BusinessAI MarketingDeveloper SkillsJob MarketRecession PrepAI DevelopmentStartup CostsProduct PivotA/B TestingSide Hustle
Besoin d'un résumé en anglais ?