If you are a developer, you cannot avoid learning UNIX. You may be able to get by day-to-day with graphical tools, and you will not advance your career without learning and understanding the UNIX ecosystem. To be productive as a developer is to know UNIX.
Caching is a complex topic. It can make your application perform faster, and it can also make your life living hell. Here are some things I learned from experience.
What makes me think of these things early in the mornings is the proliferation of Java*Script* as an enterprise application language. I believe using JS as a hammer to solve every problem will hound enterprise IT for decades.
We shouldn’t be recruiting developers based on some single technology they know but on what they can learn and apply in the future. A generalist developer that can pick the right tool for a given taskand articulate why they made such a decision is a lot more valuable than a specialist.
Though Java was my primary way of earning a living from about 1997 to 2015, it has long outlived the problems it solved. Java’s issues are being solved now by modern tools like Docker. Except for a few niche use cases, I no longer use Java for my projects.
Though modern computers are a lot more complex in many ways, Apple does understand the need of power users and students to explore and create.
There is no such thing as one grand unified full-stack programming language or a full-stack developer using a single tool. As a SaaS software architect, I certainly do not see some holy grail from my vantage point. We need to use tools that best meet the needs of the task — and the needs and the skills of developers who use them.
Employers do search candidates on social media — and so should candidates. No one wants to work for a company that trashes its’ former employees and candidates. No one wants to hire a candidate that trashes their former employer.
Peloton is not going to grow its hardware base. An argument can be made that everyone who ever wanted a connected spin bike or tread already bought one. I submit that they could grow app users.
If they stay in the hardware business, they need to find a way to get existing users to upgrade or pay for premium features.
The only way I could wrap my head around this code was by printing it out, taping printed sheets together, spreading it on the floor, and crawling over it using a highlighter to annotate blocks of code.