Elie Munsi pfp
Elie Munsi
@mme
If you could learn how to code all over again, how would you guys do it?
14 replies
0 recast
0 reaction

markus - ethOS - e/acc-d pfp
markus - ethOS - e/acc-d
@markus
Open up Notepad++ and start experimenting. Learning by doing
0 reply
0 recast
0 reaction

max pfp
max
@maxp.eth
Do NOT start with C++ 🙅‍♂️
0 reply
0 recast
0 reaction

Ayush pfp
Ayush
@ayushm.eth
Haven't come across a better resource than Harvard's CS50 MOOC
0 reply
0 recast
0 reaction

Kevin pfp
Kevin
@typedarray.eth
build whatever holds my interest. only "regrets" for me are 1) not starting earlier 2) doing too much solo coding
0 reply
0 recast
0 reaction

Liam pfp
Liam
@liam.eth
1. Start by reading SICP 2. Ship one project a week 3. Read great codebases
0 reply
0 recast
0 reaction

Ben pfp
Ben
@benersing
@perl learn to code
0 reply
0 recast
0 reaction

Gabriel Ayuso pfp
Gabriel Ayuso
@gabrielayuso.eth
replit, read through github repos, build lots of toy projects, send PRs to address issues on some github repos.
1 reply
0 recast
0 reaction

Courtland Leer pfp
Courtland Leer
@courtlandleer
@perl
0 reply
0 recast
0 reaction

Robert Atkins pfp
Robert Atkins
@ratkins
Pair program.
0 reply
0 recast
0 reaction

Quinton Chester pfp
Quinton Chester
@quinton
By starting with a stronger foundation for why and how code is written. I started really young (12), and had a mindset of “just change the values and recompile until I get the result I want” without really knowing why I was making the changes.
0 reply
0 recast
0 reaction

Nidhi pfp
Nidhi
@reallynidhi
I started with C++, but if I had to do it all over again I would pick an advance language, implement OOP concepts, contribute to open source and build silly projects on the go. Learn version control and collaborate with more devs.
0 reply
0 recast
0 reaction

kencodes.eth pfp
kencodes.eth
@kencodes.eth
Not CS classes in Java. After that was good though.
0 reply
0 recast
0 reaction

Patrick Atwater pfp
Patrick Atwater
@patwater
Start younger
0 reply
0 recast
0 reaction

hvdson pfp
hvdson
@hvdson
understand why design patterns are important
0 reply
0 recast
0 reaction