Programming as craft

>he thinks he's entitled to a job after just one interview
lmao
>Companies need workers more than workers need companies.
If you don't need the company why are you applying to work there then?
Besides, they don't NEED you either.
If you're not cutting it, there's 2000 more applicants thirsty as fuck for that job opening alone, and there's easily 20 more people after you during interview day.

I'm interested in it.

Its very easy to learn a new language and its syntax and its basic functions. However its hard to learn new concepts, techniques, theories.
I could say that programmers learn new things simply by programming, however I've met people with an inability to change.
I've watched tons of videos and presentations on different and newer languages and I didnt feel like I got much out of them, my job requires me to write in language XY&Z so why would I spend what little free time I seem to have to learn AB&C?

The more people apply, the more time the company expects to spend looking for personnel, hence waste money in the process, risking shitty workers.
Me, I can work freelance indefinitely.

A degree doesn't prove competency.

because they have other stuff to do

I don't think about my job outside of work hours because I got other stuff to do like go to the gym, play the piano, plan my house rewire and go hiking

>Why aren't majority of programmers interested in their job as a craft?
They code something that works from what few tests they actually run against it and then become highly opinionated about their own styles and practices. As far as most of them are concerned, they are craftsmen.

>Why do majority of programmers just come into work. Code for 8 hours. And then go home.
They want to get as much done as possible and fail to realize that work never actually ends

>Why don't they learn new practices and techniques?
They do, technically, but only when some new library or something comes out that's said to be the answer to all of their problems. Then they'll fumble around and half-assedly implement it everywhere. When it fails to work properly in production, either the library or someone else will be what gets blamed.

HR doesn't care.
They literally pick and choose people based on what college they went to.

>If you're not cutting it, there's 2000 more applicants thirsty as fuck for that job opening alone, and there's easily 20 more people after you during interview day.
Not sure where you live.
But here, it is hard to get even 1 interview per day. People with actual skills are rare as fuck.

they do? otherwise why would someone with actual job contribute to open source software in his spare time?

Those kind of people work on open source projects or their own hobby.