Machines do steal jobs - the repetitive, manual labor jobs that humans do not want. They also increase efficiency and profits for companies, leading to lower costs for consumers and investments in new industries that may not have existed before.
+1. There is literally zero negative impact on anyone's life by a hundred new js frameworks coming out every day. Ignore them. Use the ones you know and enjoy. If a new one seems to be gaining mainstream traction, spend an hour to check it out. Don't waste a second of brain activity or get annoyed with new frameworks - there is no reason.
I regularly work with relatively large JSON files (500kb - 4mb). These open and edit quickly in ST. Atom refuses to load anything over 2mb, and chokes even on 500kb files.
Yes, and most of those things are already available as modular open source tools that fit well in the Node ecosystem. Encouraging people to use one giant, closed, monolithic program for all of those purposes is not a good step forward for Node.
Seems like overkill. Part of why Node is great and so easy to get started with is that all you need is a browser, a text editor, and the terminal. I suppose for people that already use VS this is good, but maybe we should encourage them to write Node apps outside of that environment instead of shoving Node into a giant IDE.
This could be big for making dynamic web maps faster. Often we request a large array of geometries to display on a map and can only display them all at once after ajax is done. If we could display each geometry as they are loaded it would be a big improvement to perceived performance. I imagine this is the case for other kinds of data vis as well. Off to test!
It's not so much about when you work, but that you have a set schedule and routine. If you have a job, usually this is during the day. Knowing when you wake up every day that you will be working at these exact times tremendously helps your focus and production.
Very often late night, sporadic sessions are a product of, "oh crap I have to get some work done! Time for coffee and pounding out as much code as I can."
Not saying you can't be productive at night, but real production comes from day in, day out routine and dedication to the work. It's not as sexy but it's the reality of the job.
In the description of the book the author is pushing, I find this sentence, "A popular trend is to get up at 4am and get some work done before the day’s craziness begins. Others like going to bed at 4am."
Do real, professional programmers work this way? It is romantic to think of hacking away in front of a glowing screen at 3am, but I believe most work gets done during the actual work day. Often hacking at night means you are writing code but not making progress, which seems to be the problem with this "disgruntled developer".
Set a schedule, start working in the morning and stop working in the evening, and your sessions will be much more productive and produce higher quality work than these late night, crazed, caffeine-fueled sessions.