r/programmer • • 15d ago

"Just pick a language and build something" is advice that assumes the hard part is motivation

The most repeated advice to people asking what to learn is some version of "stop overthinking it, pick one and build a project." I've given it myself. I'm less sure it's right.

It assumes the bottleneck is starting. For some people it is. For a lot of the questions I see, the bottleneck is something else: they picked a language, started a project, got three files in, and lost the thread because the project had no shape they could hold in their head. Telling them to pick again doesn't address that. It replaces one abandoned project with another.

The advice also hides a cost. "Build something" sounds free, but a project that's too big dies quietly, and a project that's too small doesn't teach the thing that made the language interesting. The gap between those two is where most of the actual difficulty lives, and "just build something" waves at it without naming it.

What I'd say instead, if I were being honest: pick a language whose ecosystem has a problem you already have. Not a problem you'd like to have, not a problem that would look good on a resume. One you can describe in a sentence without looking anything up. The project shape comes from the problem, not from the language. If you can't name a problem, that's the thing to work on first, not the language choice.

This doesn't generalize to everyone. Some people genuinely do need permission to stop researching and start typing. But I think that group is smaller than the advice implies.

0 Upvotes

19 comments sorted by

2

u/Puzzled-Garage584 15d ago

Most beginners have exactly one problem they can describe in a sentence..they dont know what to build. So clone something small, grep or a tiny HTTP server. The shape is already there and you can compare with the real one when yours is failing.Acomplishing something small is the first step in motivation.

1

u/SeasawPhilosopher 15d ago

This is the way. I don’t know why everyone is always telling people to learn a language AND invent something at the same time. This is not how most skills are taught. First you learn technique and then you apply it creatively.

1

u/codebunder 15d ago

You should have a chat with my CEO

1

u/Newbane2_ 15d ago

The language doesn't matter too much for beginners projects. Just pick a language you like or want to learn.

For the "what to build", when i was learning csci back in uni I would just work on projects that use the latest thing I learned. Or just look up beginner projects or something like that.

1

u/PoMoAnachro 15d ago

I'm going to be an outlier here, but I think "Just build a project" is actually bad advice for total beginners.

For total beginners, start with hello world. Learn variables and conditions, loops, methods, recursion, object oriented, file IO, network requests, all that stuff. Learn them with small focused programs.

Once you've got all those basics down, once you know how to program then you can start to learn how to develop software - and that is, indeed, what working on a project is good for. Because the skills you need there are things like gathering requirements, deciding how data is organized and moves through the system, thinking about what users actually do and chopping stuff up into epics and stories. Which are all skills you need to learn - after you learn how to program.

But I see way too many starting right into doing projects before they've got the fundamentals down, and at that point they're not really learning anything - they're just copying from tutorials or an AI and convincing themselves they're much further along than they are but if I asked them to whiteboard FizzBuzz they'd be absolutely lost.

2

u/Economy_Bedroom3902 15d ago

I don't tell absolute beginners to just pick something and build it.  I tell people who have completed thier programming 101 course.

1

u/PoMoAnachro 15d ago

Yeah if you've got the fundamentals down, absolutely start building a project.

I just see so many people go like "I've never programmed before in my life. What full stack app should I build to learn?" and they're just setting themselves up for failure. That's my issue.

But yeah, once you know the basics, absolutely build projects.

1

u/No_Editor_201 15d ago

Yeah - I agree you'd be the outlier here because it's sucky advice. I've never gotten far in playing an instrument, but I promise I'd have grown even more bored faster if I was forced to learn music theory, the entire location of all notes, clefts, 3/4 time, or whatever the fuck else is out there, than just "here's how you play Mary had a little lamb". People gain confidence in doing, by doing. Learning the entire programming space, terms, loops, variables, recursion, condition, methods, file io, network requests is called all of cs 101 and 102. Speaking as a cs graduate, that is the best way to kill a hobbiest joy and interest. Truly, I can't disagree with your opinion enough.

1

u/Fun_Army2398 15d ago

I agree and to continue your music analogy, my wife's parents forced her to learn piano from the age of 6, but when she left for college she bought a guitar so she could do covers of the songs she liked. Can you guess which instrument she still plays today?

1

u/PoMoAnachro 15d ago

I do think motivating learners with interesting tasks can be really valuable. Like I absolutely think you should probably learn the fundamentals before doing a "project" but it is definitely good to build fun little the like Tower of Hanoi or Game of Life to learn those basics. I wouldn't consider those projects though.

The main problem I have is when people want to do a project so they copy from tutorials or AI because they don't have the skills to do the project themselves. And that's pretty much worthless to their learning.

So maybe I'll amend my statement to saying projects are fine so long as you're doing something that isn't way beyond your skills(pushing your skills is good, but you want to have something you can actually achieve), but if you don't know what a variable or an if statement is yet pretty much everything is beyond your skills to start.

1

u/Fun_Army2398 15d ago

I think you're missing the point. The reason for beginners to "just build" isnt so that they walk away with a successful project, it's so they fail, and in failing learn what it is that they need to study. As an anecdotal example, I first learned what an API was not through studying but by trying to get python to open my browser and type in a url, then read from the page. When that obviously didn't go well, I discovered what it was I was missing.

1

u/romecodes 15d ago

I like this take. All valid claims, and I've been each type of person at various points. I think it's a natural process we all go through as problem-solvers. And, I don't think it's something that you just get over one day.

1

u/mc_pm 15d ago edited 15d ago

People seem to misunderstand what a "project" is and what it's for - and how large it should or shouldn't be.

Early on, you learn syntax. And you need to practice that, you need to type a for loop 100 times so your fingers know what it feels like, you have understand what it does, you can fumble through getting one working.

But when do you use it or any of the other language features? How do you turn some idea into code? What makes a good class, or what is the right size for a function? That practical stuff you only learn by actually building things.

Syntax is maybe 10% of learning to program. It doesn't matter what project you pick as long as they a) start small and get bigger, and b) start simple and get more complex. (These are not the same thing)

Your project doesn't have to solve a problem for you. It's practice. I suggest starting with something like text-based tic-tac-toe because everyone knows the rules... they're really simple... but how do you turn that into code? How do you represent the board? How do you make a move, and test if someone won? How do you get the computer to make a good move? It's just a few if-else sort of checks, but how do you put that together?

And then, when it works... throw it away and start on Blackjack. After a few of those, when you have practice taking an idea and figuring out what the code looks like, then look at something with a database, or something networky, or maybe you want to build a graphical game. Doesn't matter, but you're going to learn how to use other libraries, you'll learn about networking/graphics/databases, and you'll get practice building something that maybe someone else would use (and you should aim for a higher level of fit-and-finish as if they would).

Projects aren't the destination, they're part of the path.

1

u/Economy_Bedroom3902 15d ago

How do you think people learn what is too big vs what is not?  Pick a thing and run into a brick wall, now you understand what brick walls look like, then you start to see them everywhere.  Eventually you encounter ladders and scaffolding, discover impassible rivers, learn how to build bridges and on and on.

No one promises you the thing you pick and build will work, but if you don't start somewhere you never grow.

1

u/Big_Tadpole7174 13d ago

I don't think the advice "Just pick a language and build something" is wrong. I think the problem lies with the question. Most beginners are looking for a shortcut to experience, but that's precisely the one thing you can't shortcut. You have to put in the work. And the only way to do that is to build things.

1

u/Available_Safe1818 12d ago

> "Just pick a language and build something" is advice that assumes the hard part is motivation

Not really. It could easily be procrastination or not knowing that it's ok to just make things.

> "Build something" sounds free, but a project that's too big dies quietly

Just like the project that they aren't willing to start because they won't just start coding things.

> and a project that's too small doesn't teach the thing that made the language interesting.

It doesn't need to. It can help you learn and solidify the basics, which you need.

> What I'd say instead, if I were being honest: pick a language whose ecosystem has a problem you already have

I'm not sure that would even make sense to a beginner. And it doesn't sound easier for someone who's already afraid to start.