I recently got a LinkedIn invitation from a random person. After accepting it I got a message from this person. It said:
Hey Silvestar! I recentl...
For further actions, you may consider blocking this person and/or reporting abuse
When I started, I was a little kid hacking along on a Z80-CPU in Mallard basic and assembly. I was almost instantly comfortable, but my childish experiments, though they worked, were not really elaborate. Later I learned other languages and switched to x86.
The more complex the challenge, the more I had to learn and the longer it took me to get comfortable, until I specialized in front-end and became a senior developer, so I can comfortably rely on my experience and the ability to learn new things. Still, it can take between a few minutes and days to become comfortable with new things.
Very similar experience here, starting on a zx81 in basic and then a TRS-80 in asm.
Almost 40 years into coding. More than 20 years professionally. Comfortable? Sorry to say this: still not.
I think the main problem is things get harder the further you progress.
Jr Devs always have a wide eyed approach to learn & rebuild everything. Most Sr of Devs say: "Only thing I know for sure is... I don't know anything or everything." But is comfortable with that. 😼 Just getting sh*t done. As those legacy tools that seem a mess have a history of bug fixes & testing.
Yeah. I guess this puts it perfectly.
I got comfortable with coding once I started writing unit tests. I started to internalize things like the Law of Demeter and Command / Query Separation because I found myself needing to do "too much" to test a function.
I basically learned to code a bit when I was ~13, but based on my personal journey with the whole craft, it mostly didn't "click" until about a decade later. I had already resigned myself to "it's cool that I sort of know how to code, but I'm not a real coder"...
It took beginning a career I didn't really like to convince me to really give coding another look in case it could really click.
Happened to me today after I received a resignation later from a colleague. He had quit his job to learn coding and we as remote startup company had given him access to real word projects and resources, but after 5 months he lost his nerve because he saw it as unfruitful, hectic and painful. He is more than willing to secure his old job in order to pay bills.
I think there's a quote that be like this
" Comfort is the enemy of achievement"
Just read an article about discomfort, few mins ago, the title says
"Want to Be Successful? Don't Chase Success, Chase Discomfort"
My Two Cents.
I started coding last year, and I can tell you I am not yet comfortable with coding.
Learning a programming language has never been easy for me. Most times, I try implementing the language in a real-life project. But I end up crashing out.😟
As soon as I get comfortable, I overextend myself in something that is outside my comfort zone. For example, I enjoy learning a new programming language every year. For funsies.
Many of them I learn, and never use again. Like Boo, or Groovy.
Some of them I learn, then get to use on a real project. Like Java. Or SQL.
But some of them, I learn something totally new (to me) and mind-blowing (to me). Like F#.
I think my comfort lies in "I can get it to work", but I feel uncomfortable/unconfident about "Can I get it to work better?". I think that is because it's easy to find examples of how to make code work but hard to find examples to improve your code. I think it's something you learn over time and when you work on projects of different scales.
For me maybe couple of years. The confidence grows as you see your code running in production. Maybe do some fixes.
What surprises me is every time I look at my old code because something needs to be changed, I wonder what was I smoking that time. I would definitely write it different this time. And this happens even to one year old code!
It is great fun, even after 20 years of practice.
it took me 2 years to be comfortable to coding with c++ well excatly if you see its been me 4 years html,css 1-2 years 1-2 years c++ and now python after some months after finishing the directx 11,12 learning also OpenGL therefore it depends how long it takes to learn an language and its lib's like OpenGL and other
I'm not sure I've ever really felt 'uncomfortable' with it... even starting on the ZX Spectrum as a 7 year old back in 1983, it was never scary - it was and has always been an enjoyable voyage of discovery driven by curiosity.
I've been a programmer since 1975, nearly 47 years. Now, at my age, I realize the work I accomplished through most of my career doesn't exist anymore. There is no trace of you. No legacy. All that remains is nostalgia with no one to share it with. The thing is, I don't care. The challenge of tackling the next big thing is what I enjoyed most in this profession. I'm still programming several hours a day, but now it's Rust instead of C/C++/C#, and it's WASM instead of plain old web. Enjoy the journey.
Comfortability is not the concern, its more of remembering the colons and semi colons.. Anyway, I am now comfortable in CSS, Javascript, Python and Php
I compare it with playing golf. Someday you think you got it and the very next day it frustrates you.
Having said that, it takes time but if you enjoy it then it can get easier as you go along.
Been coding for 22 years and still haven't felt myself comfort yet! It may not happen at all.
4 years
Code reviews...
Our pat answer: 1 to 1.5 years to become a Subject Matter Expert.
Took me a few months but it was worth it
GIT GUD