You get better at coding, just like any other skill, the more you do it. So yeah, it's ok to not code at home. But all else being equal, the people who do are better coders.
I think it a lot more nuanced than that. People that go home to work on github repos that are essentially just copy-pasting from HackerRank are not doing themselves any favors. I mean, sure, their repo looks better to HR drones. If that is what they are worries about, no problem.
But if they are really trying to get better, then they have to do 'deliberate' practice. Just grinding through things isn't the end-all-be-all. You have to really be trying.
I know that's a bit glib, but I think that there has been some good work done in this area of 'deliberate' practice recently. Cal Newport, Dan Coyle, Josh Waitzkin, Tom Sterner, and others have written a fair bit about the deliberate part.
> But if they are really trying to get better, then they have to do 'deliberate' practice. Just grinding through things isn't the end-all-be-all. You have to really be trying.
Not only that, but the types of coding you can do at home are often much different than your work. Most hobby projects won't give you a chance to process terabytes of data or serve data to hundreds of millions of clients or send bytes across the country with microwaves. So if your job is related to any of those things, you're not going to improve much at home.
Also, much of what companies value in software developers isn't raw coding ability. You have to be able to work with other people, understand business requirements, convince people to help on your work, etc, etc. From that perspective, somebody who spends their evenings at bars talking to strangers might be building more important career skills than the person who codes all night.
> Not only that, but the types of coding you can do at home are often much different than your work. Most hobby projects won't give you a chance to process terabytes of data or serve data to hundreds of millions of clients or send bytes across the country with microwaves. So if your job is related to any of those things, you're not going to improve much at home.
Then again, most jobs won't give you that chance either.
It can be that coding hobby projects can be your only chance to learn how to write good, readable, maintainable and performant code. If your job involves churning out features for customers or closing tickets, you will not have time for anything other than "your best under time pressure". Hobby projects can give you opportunity to improve the quality of code you produce by default.
Yeah. I use markdown hosted file and do the markdown -> html conversion entirely clientside via http://dynalon.github.io/mdwiki/#!index.md. I don't think it's possible to do that at all with orgmode?
>Remember that you are still creating software - you are just doing it through others.
Managers should not be creating software. Directly or indirectly (unless you're a product manager or in a position where you have to take PM responsibilities). I've had too many managers try to insert themselves in design decisions, micromanaging and what not. Managers should be managing people. Making people happier and more productive and communicating what your people can and cannot do with the higher ups. Even deadlines and milestones, etc should be PM responsibilities, not dev managers.
In a software company you can make the argument that everyone contributes to the process of making software. I would say that managing resources towards the development of a product IS indirectly creating software.
Lifetime is very misleading. I expect smartphones and apps to become obsolete over the next 40 years. Just like pretty much everything software from 40 years ago is obsolete now.
As an example of a tech, if someone asked me would you want self driving cars to succeed if you could not profit off of them, I would say that's a resounding success. A lot of people are excited about this tech because of the improvement in their daily lives, not because of a profit motive. Compare that to crypto
The right question would be: (assuming that there isn't already a monopoly) would you want one specific VCS to gain a monopoly if it was one you have no experience in it? (and all your mastery of other VCS would so become worthless)
