When computers were invented, a lot of the people involved were already adults - plenty in their 40s and above. Before home computers, you didn't get to use a computer until your 20s. Therefore, the first few waves of programmers included a lot of "already olds." This is always overlooked as evidence that older people can learn to program.
How I learned to code in my 30s
171–180 of 208 posts
Re: How I learned to code in my 30s
#172I've been programming for 13 years. I started when I was 14 years old and studied software engineering at university. These days, when I take on well-paid contract work, sometimes I find myself working alongside people who only started learning to code at around 25 and never went to university. It's upsetting for me to think of all the fun I missed out on in my early life because I was learning programming and pushin…
The skills I learned that don't relate to coding are how to effectively work on a team, how to handle extremely stressful situations (no situation will compare to pushing tin in Iraq), how to lead and have people wanting to follow, how to communicate verbally and in writing, how to just do something without seeking approval etc... I could go on.
Just because you spent the past 13 years learning numerous technologies and missed out on fun doesn't mean those of us who learn to code later in life aren't as valuable. We have skills and talents you might not see but are deemed equally as valuable to our employer.
Re: How I learned to code in my 30s
#173Earlier quoted context omitted.
It looks like you've learned a lot, but a lot of people are going to criticize you based off your design skills. Frankly, it's ugly so you're automatically not going to be doing any product work. If you could clean up your demos to look more acceptable to the modern day reviewer, I think you would have better presented yourself.
I considered using a common framework, but I wanted to create some design from scratch. I know it is not good for some people, but I think it added to my skills doing that way. Someday I will try to improve it, but still using my own ideias, to see if it gets better. But with the job now and all I have to learn, it is not a priority. If I were to create a product, I wouldn't try to be creative. I would just use some…
Re: How I learned to code in my 30s
#174Earlier quoted context omitted.
Isn't the same ageism -- true or perceived -- in all industries? Would you be feel comfortable starting med-school in your 30s? A PhD? Training to be a plumber or an architect? If anything, because programming takes a shorter time to become productive (say 2 years), I would think it would attract older job switchers. (edit: Before people give me counter-examples, note:I know these things do happen)
> Isn't the same ageism -- true or perceived -- in all industries? Hmmmm... in a handful of industries I might say yes, but in many others I would say no. I see an abundance of discrimination against younger in many industries. Either they are looked at as lacking knowledge, experience, or both. Often times this perception is justified, but often it is not. Of course, there is no legal recourse since age discriminati…
Re: How I learned to code in my 30s
#175Earlier quoted context omitted.
Isn't the same ageism -- true or perceived -- in all industries? Would you be feel comfortable starting med-school in your 30s? A PhD? Training to be a plumber or an architect? If anything, because programming takes a shorter time to become productive (say 2 years), I would think it would attract older job switchers. (edit: Before people give me counter-examples, note:I know these things do happen)
> Isn't the same ageism -- true or perceived -- in all industries? Hmmmm... in a handful of industries I might say yes, but in many others I would say no. I see an abundance of discrimination against younger in many industries. Either they are looked at as lacking knowledge, experience, or both. Often times this perception is justified, but often it is not. Of course, there is no legal recourse since age discriminati…
Re: How I learned to code in my 30s
#176At 31 I took my savings for my house, quit my robotic customer service job and started a startup. I worked on my 1st startup for three years and along the way taught myself front end development and design. Which I now do for a living. I say startup and if it fails like 80 to 90% due you gained an in-demand skill that you can use to make a nice living.
Would you have any advice especially on how to master design skills and how to deal with pressures around personal finance when starting out on your own? I'm about to quit my job in 'enterprise' software development because I am bored to death.
This is what I did and it allowed a three year runway to try and make it happen.
It didn't happen in terms of a financial success but it was a lot of fun! Way more then working for the man in any field!
Re: How I learned to code in my 30s
#177Is a full stack person still realistic with today's web technologies? I mean to build up expert level skillset, you'd have to really dedicate your self into learning the particularities of not just languages but also their runtime environments. Unless you have no life, and only sleep, eat, code, or super intelligent, being able to absorb and stay current with everything..... Other than that, I just don't see the full…
The value of being a full stack dev is not to be an expert in everything, as you're right that isn't really feasible. The value comes from being able to do a good job at each piece, so that you can take an entire project from concept to completion. Most full stack folks naturally develop areas of strength and focus within that, either frontend or backend, but still benefit from the fullstack context and mindset. That…
Re: How I learned to code in my 30s
#178Earlier quoted context omitted.
This is Quincy with freeCodeCamp. Congratulations on your new job, and your diverse portfolio. Getting a job as a new developer after only 4 rejections is a great batting average. Sean Smith rejected 192 times before getting a job at Trustar. https://medium.freecodecamp.org/how-i-learned-to-code-and-ea...
Sean Smith's story is so inspiring. It teaches us that if you can afford to work unpaid for 7+ hours per day, 50+ hours per week for a whole year and move to one of the most expensive cities in the world without a job, then you can truly achieve anything.
Re: How I learned to code in my 30s
#179Earlier quoted context omitted.
It looks like you've learned a lot, but a lot of people are going to criticize you based off your design skills. Frankly, it's ugly so you're automatically not going to be doing any product work. If you could clean up your demos to look more acceptable to the modern day reviewer, I think you would have better presented yourself.
This is constructive and honest opinion. Why downvote?
Re: How I learned to code in my 30s
#180Earlier quoted context omitted.
It looks like you've learned a lot, but a lot of people are going to criticize you based off your design skills. Frankly, it's ugly so you're automatically not going to be doing any product work. If you could clean up your demos to look more acceptable to the modern day reviewer, I think you would have better presented yourself.
This is constructive and honest opinion. Why downvote?