Web: Single Page Application Is Not a Silver Bullet

Seva Zaikov - Single Page Application Is Not a Silver Bullet:



Single-page applications are everywhere. Even blogs, simple html pages (in the beginning something like https://danluu.com/), have turned into big fat monsters – for example, jlongster’s blog has 1206 stars at the moment of writing, and not because of the content (people usually subscribe to blogs rather than star the source): the only reason is that once he implemented it using React & Redux. What is the problem, though? He wants, he makes it, no questions here. The problem is that it is considered normalto make blogs for reading so bloated – of course, there are some people who complain, but the general response is utterly positive. But who cares about blogs – the problem is that nowadays pretty often question is not “to SPA or not to SPA”, rather “which client-side framework should we use for our SPA”.



'via Blog this'

Choosing an HTTP Status Code — Stop Making It Hard – Racksburg

Choosing an HTTP Status Code — Stop Making It Hard – Racksburg:



'via Blog this'

Why Raspberry Pi isn't vulnerable to Spectre or Meltdown - Raspberry Pi

Why Raspberry Pi isn't vulnerable to Spectre or Meltdown - Raspberry Pi: "Over the last couple of days, there has been a lot of discussion about a pair of security vulnerabilities nicknamed Spectre and Meltdown. These affect all modern Intel processors, and (in the case of Spectre) many AMD processors and ARM cores. Spectre allows an attacker to bypass software checks to read data from arbitrary locations in the current address space; Meltdown allows an attacker to read data from arbitrary locations in the operating system kernel’s address space (which should normally be inaccessible to user programs).

Both vulnerabilities exploit performance features (caching and speculative execution) common to many modern processors to leak data via a so-called side-channel attack. Happily, the Raspberry Pi isn’t susceptible to these vulnerabilities, because of the particular ARM cores that we use.

To help us understand why, here’s a little primer on some concepts in modern processor design. We’ll illustrate these concepts using simple programs in Python syntax like this one..."



'via Blog this'

GitHub - jwasham/coding-interview-university: A complete computer science study plan to become a software engineer.

GitHub - jwasham/coding-interview-university: A complete computer science study plan to become a software engineer.: "This is my multi-month study plan for going from web developer (self-taught, no CS degree) to software engineer for a large company.



This is meant for new software engineers or those switching from software/web development to software engineering (where computer science knowledge is required). If you have many years of experience and are claiming many years of software engineering experience, expect a harder interview.

If you have many years of software/web development experience, note that large software companies like Google, Amazon, Facebook and Microsoft view software engineering as different from software/web development, and they require computer science knowledge.

If you want to be a reliability engineer or operations engineer, study more from the optional list (networking, security)."



'via Blog this'

Serverless and Deployment Issues – Paul Johnston – Medium

Serverless and Deployment Issues – Paul Johnston – Medium:

Currently, deployment tools give us monolithic deployment scenarios for Serverless.

This is unfortunate, but a direct consequence of utilising tools that aren’t built for a Serverless deployment.

We’re in a bit of a waiting phase before someone develops much more granular deployment tools.

Until
we have tools and infrastructure providers that allow us to do things
like blue/green and canarying on functions in a relatively simple way,
then we’re going to have to roll our own tools to deliver this. It’s not
easy, but it’s what we’ve been doing for the last couple of years
anyway.

'via Blog this'

How I got to 200 productive hours a month

How I got to 200 productive hours a month: "When improving your productivity, don't expect it to increase in a week because the brain needs a lot of time to restructure to new behaviors. Instead, set a small performance goal like "get 5% better each month." Aiming for faster results will make you too stressed out, while productivity requires a calm mind and a well-rested body. Be tough on your ineffective habits, but please be easy on yourself."



'via Blog this'

LinkedIn's Tips for Highly Effective Code Review - The New Stack

LinkedIn's Tips for Highly Effective Code Review - The New Stack: "In summary, having a formal code review process helps improve code quality, team learning, and knowledge sharing. The quality of work increases when every engineer on the team realizes two important things: someone else will read my code, so it better be good, and I’ll have to address any review comments I receive, so I should try to make my code good the first time around to save myself effort later on. When code reviews become an everyday habit, the team practices giving and receiving feedback on a daily basis. This is key for growth and improvement."



'via Blog this'