21–30 of 155 posts
Earlier quoted context omitted.
I think it's a mindset thing; either you have the mind of a developer or you don't, degree or not. I'm self-taught, and early on I had a inferiority complex when it came to those with CS degrees. Didn't take long for that to wear off as reality exposed gaps in their ability/knowledge.
Fair enough. I have a Software Engineering degree (certified Engineer), so I already have a superiority complex anyway ;)
What a terrible advice.
"But I’d never even heard of the words front-end developer or full-stack. What was Heroku? Never heard of Xcode. Wasn’t git just the thing you used to make sure your partner had access to the code you’d written? Frameworks? Didn’t you just need HTML and Javascript? What the hell was an API?!" If you literally never heard about any of those during your computer science courses, you attended a sad, sad university.
I currently work with a bunch of people who are "business majors" or whatever and are similarly self-taught in the Tech/IT/Programming space. It's interesting to watch how they work and the kinds of outputs they produce. Quite a lot of the stuff works... mostly... It's entirely untestable, not repeatable, undocumented and just stuck together with flaky glue code. Sure, if you aiming to "make it work" you can do that.…
I'll argue that good programmers need to have a working understanding of algorithms, databases, compilers and all that. Sure, it's not something you will use day-to-day in a software engineering job but it's important to know how all the low level pieces of your stack fit together in order to write good code. There's nothing worse than a programmer that fits together code snippets from Stackoverflow and similar sites…
I think it's fair to say that you can be effective without necessarily being good and vice versa. I think the some of the best developers are those who are smart enough to have gotten a CS degree but skipped a bit of the academics. (A bit self serving: I graduated high school in 1996, had my first intro IT job by the fall of 1998, and had my first real programming job in January 2000, while my contemporaries were sti…
>Some Small Advice: if you’re just beginning to program, I’d suggest starting with JavaScript/HTML/CSS because there is a plethora of help out there. What a terrible advice.
>Some Small Advice: if you’re just beginning to program, I’d suggest starting with JavaScript/HTML/CSS because there is a plethora of help out there. What a terrible advice.
Why is it a terrible advice?
About javascript(vanilla js), nobody even wants touch it anymore. Almost anybody who interacts with javascript code does it with a 5 foot stick(coffescript, clojurescript), and/or behind huge frameworks that protects you from its perils.
Something that is more usable and understandable in its barebones state like python makes more sense for beginners.
This is very true, but it's a bit more complicated than that. "I'd come to understand that the answer was out there, somewhere." The answer is out there, but so is the wrong answer. Recognizing the right answer is the hard part. I also must point out that the answer is out there if you know English . Knowing English is a strong privilege. Success rate plummets if you Google programming questions in a language other t…
This is something I've always wondered - how do programmers who don't natively speak, read, or write English cope with the sheer amount of literature they have to parse to have a career programming?
Actually it is funny, I only realized while reading this discussion that I always google my programming questions in English. It never occurred to me do google them in Dutch. I will try it today to see the results :)
I currently work with a bunch of people who are "business majors" or whatever and are similarly self-taught in the Tech/IT/Programming space. It's interesting to watch how they work and the kinds of outputs they produce. Quite a lot of the stuff works... mostly... It's entirely untestable, not repeatable, undocumented and just stuck together with flaky glue code. Sure, if you aiming to "make it work" you can do that.…
Code that's testable, repeatable, well-documented and elegant doesn't guarantee that an application will actually meet anyone's needs in a commercially sufficient manner.
The WordPress code base is frequently criticized, and the Facebook index.php code from 2007[1] will probably make some people cringe, but these are just two of many examples demonstrating that if you want to "do well", building applications that work and meet the needs of their users is initially a lot more important than "proper technique."
Earlier quoted context omitted.
I think it's fair to say that you can be effective without necessarily being good and vice versa. I think the some of the best developers are those who are smart enough to have gotten a CS degree but skipped a bit of the academics. (A bit self serving: I graduated high school in 1996, had my first intro IT job by the fall of 1998, and had my first real programming job in January 2000, while my contemporaries were sti…
Everyone overvalues education similar to their own and undervalues education dissimilar to their own.