Live data from Hacker News

A 37-year-old wanting to learn computer science

initcoder.com

171–180 of 190 posts

Re: A 37-year-old wanting to learn computer science

#171
post #156

Earlier quoted context omitted.

“Computer science is no more about computers than astronomy is about telescopes” — Edsger W. Dijkstra

I have always found this quote annoying. There are many ways to solve problems, but when you constrain yourself to solving them mechanistically, that is what makes computer science computer science. Virtually every theoretical CS paper implicitly presupposes a specific model of computation. Sometimes they even say it explicitly. Sure, computer science is not about a specific computer. But it is definitely about compu…

> I have always found this quote annoying

"Mission accomplished." -(fake) E.W. Dikjstra

My strong impression/suspicion is that Dijkstra had a great sense of humor and also enjoyed irritating people; it's puzzling when people take things like his comments on programming languages as serious rather than tongue-in-cheek, but I suspect he would have been amused.

I learned today that apparently Dijkstra won the Dijkstra prize in 2002. (I'm not sure what the qualifications are, but if I were to choose then it would be awarded to the most brilliant, and irritating, computer scientist who has made a groundbreaking contribution to a particular field.)

Re: A 37-year-old wanting to learn computer science

#172
post #161

Earlier quoted context omitted.

I'm sorry it didn't work out for you. Sometimes it's luck of the draw. It also depends a lot on which industry you're in (finance, gaming, etc.). As an extreme example, if you're any good at COBOL, you can probably get a job working on legacy systems regardless of your age. Gaming, probably not so much. You may have more success getting smaller freelance jobs at first and building a reputation as a can-do developer,…

Getting a freelance job is easier than getting an interview ?

No, I'm saying getting a freelance job is often easier than getting a full-time job because the barrier to entry is lower: companies don't usually scrutinize freelancers with the same eye, especially for smaller jobs, since it's much easier to let a freelancer go if it doesn't work out. Also, freelancers are usually hired based on their ability to get the work done, not so much biased metrics like age and gender. Of course, every industry is different, but that has been my experience as a freelancer for several decades now.

Although in the case of the person I was replying to, apparently even getting an interview was impossible, so YMMV.

Re: A 37-year-old wanting to learn computer science

#173
post #160

Earlier quoted context omitted.

I would argue that even if other people have designed an entire system and "all" that is left to do is to write the code, things can go very wrong if the coder isn't good at designing their code well (e.g. to be efficient, robust, etc.). It's "design" all the way down; there is no imaginary line where design stops and coding starts.

thats true, if there were one sigle "coder" who was cloistered away from the team and came back when s/he claimed the requirements were met and the task was complete. Whereas, in FDA (and presumably FAA/DoD) regulated designs, a massive team is following a rigid SDLC including code reviews for best practices. Now, technically the FDA doesn't force that, all they specify is that some standard procedure must be followe…

> a massive team is following a rigid SDLC including code reviews for best practices

Regardless of how thoroughly a system is planned in advance, programmers are not automatons who mindlessly fill in the last few blanks. They must make choices about the code they write, and that is absolutely a part of the overall design. If that code fails a code review, well, then it gets rewritten, but that's ancillary to my point: programming is design (albeit at a lower level than the overall system design).

Re: A 37-year-old wanting to learn computer science

#174
As you know, getting an entry-level job at your age will be very hard. Your best bet is to look at what employers are seeking by examining current job openings and using them as a guide for what to study. Try to identify the fundamentals you need to learn. I would even recommend applying to see if you get any responses; even securing an interview would be a plus. This will help you get prepared for your real job search once you are ready.

Find a job at a company, any job you qualify for, that has an IT department where you want to work. Make friends in the IT department and see if you can get the manager there to offer you an entry-level position once you learn what you need to know to do the job. Being a good employee in one department can take you a long way if you want to transfer to another.

Additionally, give yourself a deadline. Do not leave it open-ended; it's too easy to meander and get nowhere. It's also unfair to your wife to carry the load indefinitely. Plan out your journey before you quit your current job and stick to it.

FYI, programing as a job is no where nearly the same as programming as a hobby. The job is full of pressure to get things done and you write code you may have little interest in.

Good luck!

Re: A 37-year-old wanting to learn computer science

#175
My immediate thought is that you do not need to learn “computer science”.

It is for academics, those looking to differentiate themselves from the other 2000 CS equipped applicants for a job, those wanting interviews answering useless data structure and algorithm questions, and those writing applications in the domains of the computer and data sciences, and computing infrastructure.

Most software is outside of this, though that might surprise many HNs who assume that is the only type of software there is. Well maybe they will cough up “crud apps” if pushed.

Just learn to program and learn the applicable standard libraries associated with a programming language. Stop overthinking it. An 8 year old can do it - you can too.

Re: A 37-year-old wanting to learn computer science

#176
Coding isn't really the hard part. I learned it on a commodore with casette tapes.

Sure you need the general sense for architecture which comes from experience, but it is not a long list. Learning about computer hardware and assembly from scratch is what made it all come together for me. Algorithmic complexity, data structures, development tools were all a mystery and "just things to memorize" until I learned about logic gates, developed transistors from those logic gates to get memory circuits, developed binary full adders, a bus, a basic cpu with a few registers and a program pointer and actually programmed it with its own instruction set. All you really need for this is pen and paper. Then move on to multicore, multiprocess, scheduling, then move to simd and graphics hardware. If you have several months to dedicate, I'd say go for that.

Re: A 37-year-old wanting to learn computer science

#177
post #156

Earlier quoted context omitted.

“Computer science is no more about computers than astronomy is about telescopes” — Edsger W. Dijkstra

I have always found this quote annoying. There are many ways to solve problems, but when you constrain yourself to solving them mechanistically, that is what makes computer science computer science. Virtually every theoretical CS paper implicitly presupposes a specific model of computation. Sometimes they even say it explicitly. Sure, computer science is not about a specific computer. But it is definitely about compu…

> There are many ways to solve problems, but when you constrain yourself to solving them mechanistically, that is what makes computer science computer science.

How would one solve a computational problem non-mechanistically? Even if executed with pen and paper, or sticks scribbling on sand, any algorithm is still mechanistic.

Re: A 37-year-old wanting to learn computer science

#178
post #90

Earlier quoted context omitted.

Can you share that strong evidence?

Oof, no, I can't. I'd edit my comment, tempering that certainty, if I could. I recall multiple therapists telling me precisely that, according to the research, people are less likely to accomplish or make progress on passion projects when they quit their jobs with that goal in mind. I have memories of finding papers on this, too. Now I can't find them, and I'm questioning the accuracy of my memory. Disheartening and…

"Thanks for the reality check."

My speciality, you are are welcome.

I can only share anecdotically, that for me having 2 jobs did not worked out at all and I only started to make progress on my passion project once I quit all the other stuff. On the other hand money was tight and stress

So it probably depends, on the stress level of the ordinary job. If it is something that brings money but leaves you energy, it might be the better alternative to have more time but existential fear which blocks passion for me.

Re: A 37-year-old wanting to learn computer science

#179
I was 37 last year when I finally got frustrated with my job and started to learn Python. Took a couple of open for all MOOC’s. Decided that damn this is cool and took math and alghorithm’s as well. Now I was accepted to the same university where a certain guy called Torvalds created Linux. I have written countless Python scripts and apps past year and am now learning C to actually make stuff I want to (OpenGL shaders, games, low code stuff, audio hardware). I also was diagnosed with ADHD some years ago. Therapy helped a lot to manage my issues in focus etc.

So it can be done! However, I had already been working as a tech (not programming though, more networks and sales tech support) for years, so it’s not like I had to learn what a CPU is.

Re: A 37-year-old wanting to learn computer science

#180
post #108

I didn't draw a single piece of PNG until i am 38. Now i am about to release my second solo developed game. My art is nothing great, but a year a ago wouldn't even believe i could draw a single sprite. https://www.instagram.com/arcadenest_games/ I find my age to be great period to learn new skills. It is never too late.

Not bad! Nit: I think your moon is a bit too rough on the edges. Did you try a smoother edge?

That's because of pixel perfect rendering is not handling rotations and position changes great. It looks fine in motion, but i can improve with using semi transparent pixels on the edges.
Post reply on HN