Working from home as a software developer/engineer, what will it be in a few years time? Which things became fundamentally different already, and which will change history? Let's embrace the new situation rather than planning come back to the norm.
There is plenty of information about Azure on the internet. However, a lot of it is written as marketing material or simply outdated. When it comes to real tasks, it turns out that much of those scripts and tutorials no longer work. This Q/A session with Elkhan Yusubov is covering key terms behind Azure, to set a good start for learning on your own.
An interesting article comparing simple common tasks done with React and then Blazor. With code samples. From Telerik blog, but good stuff, not written as ad.
My summary of MS Build Day 1. Keywords - Terminal, PowerToys, Microsoft NPM, Code Spaces, Live Share, Surface Book 3, Teams running on Azure, Static Web App template, HTTP REPL, Power Apps Studio, Azure Synapse Link, Project Cortex, VEGAS Stream, Fluid framework, WebView2.
To explain what style encapsulation means, we will look at how Angular does it. On this screenshot an h1 style is converted to _ngcontent-lvy-c0 class during compilation, and so it does not leak out styles to other components and the app. You can declare another h1 style in another component and that will not have any effect on this component, guaranteed by Angular. Or its children, which might be even more important (so it's more than just nesting css in an HTML selector tree).
There is very little information about Blazor on the internet. Even less as far as enterprise / professional Blazor development is concerned. Blazor is not exactly new, but still, it feels more as an undercover platform, even today in May of 2020. This Q/A session with Tim Corey is meant to fill the gap. Tim is a software developer, consultant, trainer, and Microsoft MVP. He runs a YouTube channel dedicated to making the process of learning software development easier.
First and foremost, this is not an article to brag about how cool it is to be a freelancer. This is just the cold truth about the issues no-one is talking about. What it can be like, what you need to prepare for, if you consider becoming one. The views expressed here are exactly my own, you are free to disagree and post your ideas in your own blog or another public resource. The goal is to help other developers who are struggling in their career. Help them understand they are not alone with those problems. So let us get started, shall we?
How do you recognize a good developer at interview stage? Are they excited by learning new things or are they tired from it? Do they wake up and realize they still have not yet learnt everything they could? Or do they always know enough to just get by? When technology becomes obsolete every 2 years, 20 years of experience helps little. You are great at writing loops? Sorry folks, now we do functional programming.
There are several stages of maintainable code, each suitable for a particular situation. Let us call each stage a maintainability level. The higher the level, the more maintainable code is, and the more time it takes to write in this way. Do you always need the best possible maintainability?