I'm curious to know - what site is that?

Nice post, but you're being pretty lazy here :)

it's a copy-paste of that other Reddit post. The original Quora post can be found here.

Oh, I now see what you mean.

I just thought that employers/companies would be able to distinguish good from bad developers. If not, then the hiring process is broken.

I've never taken "boot camps" or video-based programming courses, so I can't speak about them.

To be honest, when I went out of college, I thought that I knew how to program. But in retrospective, I didn't know that much. And my code was certainly not of the highest quality. I learned to program well in my first few jobs.

In my opinion, the same applies to "boot camps" or online courses. You learn the basics. You might think that you know a lot, and that you're good. But you really learn how to code in your first few real jobs.

What do you think?

Sorry to say that, but it looks like blogspam.

There are already many resources that show how to create a "Share" button for Whatsapp. Here's an example.

What additional benefit(s) does your post bring to the table?

I think that most arguments have been discussed on Reddit and Hacker News already. But mine is a bit different.

Many people assume that it's creator's job and responsibility to rewrite curl in another language, and in his spare time. I just don't agree with this. If people want a "better", "safer" or "more stable" curl, then they're free to rewrite it in their favorite language.

I see a few possible reasons why there are so few women in programming:

• For them, staring at a screen all day long is extremely boring and uncool.
• It isn't aligned with their biological imperatives. It's well known that women tend to be better at communicating and forming relationships than men, so they may be more attracted to fields that will allow to them to leverage those skills.
• There's a "herd effect". Programming is "seen" as mainly a man thing by other women, so they don't pursue it.
• It's a very harsh world for different reasons, and they've already heard about it.

Why are there so few men in nursing? The reasons are probably similar.

I had only a vague idea of how Git commits are stored. Now I know. Thanks for sharing!

I agree with you; it's unreasonable to expect a developer to be an expert in all tools and technologies (back-end and front-end).

In my opinion, a good developer is somebody who's versatile enough, and who can learn on the spot, whenever a new technology is required.

How good is your knowledge of HTML, CSS and JavaScript? And what about programming is general?

This is just a feeling of mine, but if you're asking what "CSS program" you should use, perhaps you're missing the basics.

1. Grab a good text editor and a browser (Notepad++ and Chrome will do the job).
2. Read a few books about those topics and complete the exercises. The "Head First" collection from O'Reilly is quite good for beginners.
3. Create your first website or blog. Customize its look using HTML and CSS. Perfect it.
4. Then write your first web app - to do that, you'll probably need to learn a new language for the backend (Node.js, Python, etc.).

N.B.: You don't need a separate program to "style" HTML markup. You just need to edit a CSS stylesheet with a text editor and view the results in a browser. After going through the bullets above, you should be able to do it.

I see recursion as a very useful tool. But it shouldn't be used in all cases.

In my opinion, if it leads to more elegant and more maintainable code, then you should use it. Be cautious, though; you should limit the depth of the recursion.

But there are cases where recursion is simply overkill, or will lead to unnecessarily complex code; then it should not be used. A stack-based approach should be used instead.

I generally "feel" when recursion is needed or not. I generally find it a bit harder to understand at first, but then it becomes much more clearer.

Super interesting post.

The highlights for me are:

• "You have to document the why."
• "Don’t code “your way”. Just follow the coding standards. Make your code predictable and easy to read by coding the way people expect."

There's just one exception related to the last point, I think. Each company has their own coding standards, and those standards are made to be improved over time; they should not be stagnant, as if they had been written by God himself. So we should be free to be critical of them, and to change them whenever it's really needed.

When creating a prototype of something, I agree with you; unit tests are often overkill.

However, as soon as your program becomes more complex, I find that unit tests are necessary. Otherwise, it's too easy to introduce regressions. After all, a programmer can't think of all possible corner cases at the same time.

If you can afford it, take a break or vacation for as long as you need.

Otherwise, leave your job and work on projects that you love for a few months. Then you'll see what you need to do next. And most likely, you'll feel motivated and refreshed :)

• Windows 7 desktop with Putty/SSH, Notepad++, Pycharm, TortoiseGit
• CentOS 7.X VMs to deploy code on.

Personally, I would say that it depends on what you want to specialize in.

If you want to be an embedded programmer, then you'll have to learn the underlying OS used by the devices that you deploy your code to. It most likely won't be Windows. So learning Linux and Linux programming is certainly a good bet; it will make you a more versatile programmer also.

I don't know anything about programming for the finance industry. But I'm not sure that C++ is the right tool for the job; it's a bit too low-level in my opinion. Would Python be a better option?

In any case, diversifying your knowledge and skills is important. Learning Linux programming (Ubuntu, CentOS or any other) will probably make you a better programmer overall than sticking to Windows only.

This post is interesting, as it raises a few important points and questions.

But I don't agree with the reasoning. We don't all need to be more scientific. We don't all need to master mathematics. After all, there's only a finite amount of time in a day.

I'd be curious to know why Go is becoming less popular as a "weekend language".

Is it because it's no longer the new shiny thing? Is it because it's being used more and more in a corporate context (so it's becoming less cool)?

What do you think?

The destiny of pretty much any service is to eventually disappear, so yes, it's a dead-end. However, solution #1 would allow us to avoid such problems in the future. It's a great solution, actually!

Personally, here's what I would do:

1. Read a few books about programming languages (Python, Go, etc.) to really understand how it works behind the scenes (i.e. backend stuff).
2. Start a personal project in one of those languages and complete it.
3. Read a few books about web development (HTML, CSS, JavaScript) to understand how it works.
4. Read a book about a specific web framework (e.g. Flask).
5. Start a personal project combining the technologies and languages that you've learned, most likely a complete web app (backend + frontend).

Then you'll have a pretty good understanding of programming in general. This is just a starting point of course.

These days, I'm still learning a lot about Python. I've been working on a distributed web crawler as a side project and I've learned quite a lot in the process (not just about programming, but about various other things like how the web actually works, how search engines work, SEO, etc.).

Also, I started a programming blog a few months ago, so I've been learning how to write better and more interesting posts. IMO, it's highly complementary to a programmer's job.