21–30 of 58 posts
On Coursera, every course I've taken has used the programming language as a means to an end, not an end in and of itself. Perhaps the author should Google online courses more extensively.
>>> Whenever you have to google some error message or problem, read all the answers. Get as much context as possible on your problem, and do not be satisfied just with having come across a solution. This is a fatal flaw. Considering a TON of JS frameworks are so new, there just isn't a whole body of data on issues people are experiencing. I don't how many times when React started getting traction, I'd google an issue…
If you're googling something about Linux it's even common to find that none of the answers fits your context.
The more "full-stack" I get, the more I just hate all stacks. Everything turns to shit if you give it long enough.
I couldn't disagree more with this entire article. > the self-taught web developer knows surprisingly little about the web’s underlying technology. I know very few developers who aren't self-taught. In reality the opposite seems to be true. It's the developers who take a course and don't continue learning that stall. This is something technologists (even non-developers) absolutely _need_ to do -- self-teaching. The a…
Yes.
I'd add: anyone smart enough to be considered an expert in any subject will eventually find other subjects to explore. I'd argue this helps them become a better developer, more than coding in their spare time ever would.
>I have met many programmers that don’t like to code in their spare time, and that has reliably revealed them to be sub-par developers. Whatever little credibility you had up to this point you've just lost.
Earlier quoted context omitted.
Not exactly, because someone who explores other technologies unrelated to his/her "work" field will inevitably pick up experience and knowledge - which the employer can grab for free without sending the employee to expensive courses or having to hire highly specialized freelancers. I have done a lot of weird things as "hobby" projects with even weirder technologies, including interfacing with smartcards in PHP (don't…
> Not exactly, because someone who explores other technologies unrelated to his/her "work" field will inevitably pick up experience and knowledge - which the employer can grab for free without sending the employee to expensive courses or having to hire highly specialized freelancers. I don't think there is any debate that, in general, someone who tinkers, explores, and codes outside of work will be relatively better…
I've found that the truth of this depends almost entirely on the type of coding one is doing at work.
If you're doing challenging work all day and then do some challenging work after hours, you'll likely be better than most based on the sheer amount of practice.
If your day job is mostly a joke and you are maintaining systems that you don't really understand, coding all night won't make you better than someone who is doing challenging work all day and logging off entirely at closing time.
Earlier quoted context omitted.
> Not exactly, because someone who explores other technologies unrelated to his/her "work" field will inevitably pick up experience and knowledge - which the employer can grab for free without sending the employee to expensive courses or having to hire highly specialized freelancers. I don't think there is any debate that, in general, someone who tinkers, explores, and codes outside of work will be relatively better…
>I don't think there is any debate that, in general, someone who tinkers, explores, and codes outside of work will be relatively better than someone who doesn't. I've found that the truth of this depends almost entirely on the type of coding one is doing at work. If you're doing challenging work all day and then do some challenging work after hours, you'll likely be better than most based on the sheer amount of pract…
I couldn't disagree more with this entire article. > the self-taught web developer knows surprisingly little about the web’s underlying technology. I know very few developers who aren't self-taught. In reality the opposite seems to be true. It's the developers who take a course and don't continue learning that stall. This is something technologists (even non-developers) absolutely _need_ to do -- self-teaching. The a…
>I have met many programmers that don’t like to code in their spare time, and that has reliably revealed them to be sub-par developers. Whatever little credibility you had up to this point you've just lost.
ps. if you have to spend all your free time studying to avoid losing your job, you never actually had any free time to begin with.
So I know one half, but I know it well. Yes, I've heard of front end frameworks, some design ideas, some CSS but I might as well say I don't. Well, so far it has worked pretty well for me.
I also heavily interviewed for my company before, and would usually be pretty leery of who claimed they are "full stack". Yes, some candidates were really good and knew both sides, but most just knew about superficial stuff on both ends (which is ok too, just not for what we were hiring).
>I have met many programmers that don’t like to code in their spare time, and that has reliably revealed them to be sub-par developers. Whatever little credibility you had up to this point you've just lost.