is 20 yo too late to learn programming ?

It's never too late.

Not even close. 40+ is where you are hitting a genuine concern, but it is still possible if someone is willing to train you.

If you work hard starting now, by 23-25 you could be guaranteed a job if you build a strong portfolio.

It takes a good month to be familiar with a language enough to do basic tasks and after that things only get easier.

t. Neet

>>58766654
>tfw proficient but haven't bothered to start a portfolio

After 16 you are essentially going to be stuck in pajeet tier programming jobs

Over 20 you are not going to make it past the interview stage in any corporation as they need young people in their twenties

Well I have a job without college. Took me 3 year of training and almost drove me insane and suicidal (not kidding). T 21atm. Still not going to collage.

it's always too late if you don't start immediately

>>58766569

No. I have a degree in mechanical engineering but started programming when I was 28. I am completely self-taught and I am now 35 working a well-paid position at a good company. I will say my engineering background did help significantly getting my job since I work in robotics, but I still had to pass a standard software developer whiteboard interview like everyone else I work with.

I do think that having some sort of formal STEM education background is important though. I did not have to blink an eye when I got into complex mathematics while I was self-teaching myself.

>>58766708
>college
>collage

>>58766683
Lies. Companies hire you based off experience. I've met people that start in their mid 30s to 40s and still school children. Its all about how hards you...

work work work work work
he see me do me work work work work work
na me do bee work work work work work
scooby dooby work work work work work.

lead programmer at my work learned how to program at 32

It's not too late and companies really don't care about age that much. The big problem is a lot of older people have issues with having a boss much younger than them.

>>58766683
oh look another LARPer who knows nothing about the real world lol

>>58766569
Yes.

I wrote my first compiler when I was 16. At 20 you're too old to start lol. At 20 I was already doing my PhD in quantum cryptography. Skipped a few classes.

Don't worry your pretty head with such things. Get a job in the food industry or something. I kind of envy people like you. Ignorance is bliss.

I sometimes imagine how life would be if I was a normie like you. You can't imagine the burden of being a genius. Sometimes it is unbearable.

If at 20 you're not 100pct certain what your calling is, you're already too late and a normie. You can still enjoy life though. More than we can actually. Life is torture for me. I am tortured by the problems I am solving. I can't just relax like you normies

>>58766867
Sure, sure.

>>58766789
>hard work
1950 wants his meme back

File: 1380120177302.jpg (1KB, 100x100px) Image search: [Google]

1KB, 100x100px

>>58766867

File: 1465675002001.gif (295KB, 1235x675px) Image search: [Google]

295KB, 1235x675px

Only if you're a Hackerman and listen to vapor.

File: d98.jpg (28KB, 600x640px) Image search: [Google]

28KB, 600x640px

>>58766867

Yes, at 20 years old your brain chemistry rewires itself so that you are physically unable to learn any new skills. That's why most degree plans build your framework within the first two years.

Sorry, you're gonna be flipping burgers for the rest of your life.

>>58766888
You can develop your own OS at 17, with GUI, etc. So making a compiler at 16 is not impossible. Especially since we are not talking about details such as quality, stability, or even what kind of compiler.

>>58766762
colliage

>>58766867
If this isn't a bait, start taking care of your health and stop eating like shit you fucking pretentious submissive purposeless monkey.

Or just end your suffering and kill yourself already.

>>58767006
neurosciencefag here, actually the brain tends to be set after 25, as it's fully formed now. You can still learn totally new skills after that point though, it'll be a bit harder. Also it depends on what you've done up to that point, for example if you learn a foreign language at 20-23, learning a new one in your 30s won't be that much harder to do: it's not a totally new skill.

>>58766569
i often find that people who do program 10y+ can suck so bad at solving problems and designing software that i would never let them touch anything i have to maintain
i also find that a lot of <25 year old people that just don't know yet how to design maintainable code or approach problems because they just haven't seen enough code and problems yet
same goes for people that worked a long time in one framework and one language and solved one type of problem over and over
i know brilliant developers who started as script kiddies, bash monkeys or excel/word automation slaves
i know people who got a masters degree and can't design maintainable code for shit
there seems to be no pattern, other then how much these people care about their work and how much experience they got
getting a developer to care about his work, studying similar approaches and solving a problem is more important to me then how good he is at codemonkey implementation that he started to lean before he was 10
i do of course try to get everyone into writing functional, threadsave, stateless, well tested, correct code that can be used for libraries and apis but obviously not everyone can do that at all times and has time for that
however there is also a place for the intern that produces a 20k line approache to a run once then forget about it problem that i would have solved in a day but does his job well and may get me to invest more time in him. also i didn't need to solve that ugly problem
investments in people are tricky, building a team and maintainable codebase is fun and part of the job
age discrimination is stupid