Review: Insight into developing Windows Subsystem for Linux (WSL)

Beautiful insight into Windows Subsystem for Linux (WSL) development and one's career in software development at Microsoft sparking a new shift in advancing technology for developers! Thanks, Tara!!

https://medium.com/microsoft-open-source-stories/when-linux-came-to-windows-204cf9abb3d6

References

• https://docs.microsoft.com/en-us/windows/wsl/faq
• Get Ubuntu on Windows

Review: Google's Fuchsia OS

If I ever begin writing software for embedded systems, for example a spaceship, then I probably want to give serious consideration to Google's new Fuchsia. I'm not at the level yet, but making note of where to find the Getting Started guide.

https://fuchsia.dev/

Cheers!

Review: Microsoft Azure mostly serving Linux

This article was cool to read. I'm glad to see that the new Microsoft continues to support the Linux world. More so, to see that they support the open source communities. This provides great insight that any Microsoft Servers will eventually be no longer supported. On the other hand, if developers (and IT) don't already know how to work in a Linux environment, then it's time to start learning and practicing.

https://www.zdnet.com/article/microsoft-developer-reveals-linux-is-now-more-used-on-azure-than-windows-server/

Reload: Visual Studio Code - Tips and Tricks

This YouTube from Microsoft Developers on VSCode was very helpful and cool. The pace of the video is quick and so I had to pay attention. For convenience, I'm adding the "Useful Links" below the video clip.

VS Code Tips & Tricks

Useful Links

1. https://code.visualstudio.com/docs/getstarted/tips-and-tricks
2. https://github.com/microsoft/vscode-recipes
3. https://code.visualstudio.com/docs/remote/remote-overview
4. https://docs.microsoft.com/en-us/windows/wsl/faq
5. https://code.visualstudio.com/insiders/
6. https://marketplace.visualstudio.com/vscode
7. https://www.docker.com/
8. https://youtu.be/tnSnVlbKtMk

Extra

1. https://github.com/microsoft/vscode-tips-and-tricks
2. https://github.com/microsoft/vscode-recipes/tree/master/Angular-CLI

Review: Evolving Role of the Modern Developer

Read Article: Evolving Role of the Modern Developer

In this article, I have come to realize that my initialize thoughts on the direction of a development between the role of a developer and a QA engineer (or tester or whatever you call the person who verifies your code works as expected) is actually correct. I was confused and thought that perhaps the role of a tester evolved into just software engineer in test (SET) because of the positions that the tech giants were creating. In addition, because I see the evolution of AI testing.

But, on the spectrum of the SDLC the roles are becoming more integrated and in some respects these roles are merging into one. This doesn't mean the SDLC is going way. How a product or service is built will still need the basic engineering principles and cycles applied. However, who plays which role while creating or updating the product via SDLC will become more versatile and need a greater understanding of the customer's expectations of the product (and not just a function or feature). And, since no single developer can remember everything about a product, developers will need to know how to kindly work well with others.

Review: Amazon Software Development Insights

How is software developed at Amazon?

There are some really good tips in this online video and article.
http://highscalability.com/blog/2019/3/4/how-is-software-developed-at-amazon.html

Review: Write Simple Code - Fast

I like how this author points out the difference between a senior developer and junior developer.

"But code is human language. It has to communicate the who, what, when, where, how, and why of a task, as well as instruct the computer. It has to make sense five years from now after the company has been acquired and a new team who has never seen this code before has to crack it open and make an enhancement or fix a bug.

Yes, writing dumb code is hard. ...I know that the best thing I can do for my team, and the future maintainers of the code, is to write dumb code."

https://hackernoon.com/why-senior-devs-write-dumb-code-and-how-to-spot-a-junior-from-a-mile-away-27fa263b101a

KISS

Basically, a senior developer writes the most simplest code - think KISS. Even better, s/he creates the simplest designs and then directs her/his team to code simply according to the simple design.

But, we do live in a real world and almost every developer is trying to gain points over another.

Good luck.

Review: Easier developing isn't actually easier

Here's an article I agree with. The speed and ease of application development doesn't make development actually any easier. The biggest concern from my perspective is developers coding while being mindful application security.

https://www.itprotoday.com/devops-and-software-development/why-easy-software-development-making-things-hard-development-careers

Learn: Microsoft Virtual Academy -> Microsoft Learn

I never heard of Microsoft Virtual Academy (or if I did, I forgot). So, glad to have read this article.
https://buildazure.com/2018/12/28/microsoft-virtual-academy-is-being-retired-jan-31-2019/

In short, learn more regarding Microsoft development at:
https://docs.microsoft.com/en-us/learn/

Review: 10 Critical Tips to Learn Programming Faster

Today's article, I'm focusing on something practical and essential for all people working with technology: 10 Critical Tips to Learn Programming Faster

I like what the author does here and her explanation is straight to the point. But, if you want to know some of the practical challenges accompanying each tip, then here's what I'll add (based on my experience).

1. Start With the Basics and Spend More Time There

• This is fundamental to learning any skill. So, don't learn just because you feel like it or it sounds cool, but learn with purpose; learn with the intent to master the skill.
• This takes time, lots of time! So, start early as possible.
• These basics can become boring if you're learning by yourself (like playing any sport by yourself). So, learn with friends and enjoy the course(s).

2. Coding by Hand is Highly Recommended

• This is a great tip for interviewing, but is practically useless. With so many programming languages to choose from and so many companies using multiple languages to suit their product development, practicing in one language might not be helpful with understanding and using another language. However, practice coding in a way to understand the programming language. Pick a few languages like industry standards such as Java, JavaScript, and SQL. Pick languages that a full stack developer would require.
• Know how to write pseudocode. With the computing industry changing quicker than ever before, it's important to switch between programming languages and still carry the function definitions and application structure over. 
• In addition, other people should be able to read and easily understand your code.

3. Fiddle Around With the Codes

• Don't just fiddle, but start exercising your creativity and figure out how to update the code. This is also called "refactoring". Learning to made code updates is a lifelong skill since most programmers must work on teams which means eventually you'll need to update someone's code - including your own.

4. Reach Out to Others for Guidance

• Make mentors that are tech gurus. It's difficult to find tech gurus, but not if you get involved in open source project like in Apache Software Foundation.
• Take advantage of online mentors (that you may never meet).
• Take advantage of community forums online like Reddit and StackOverflow.

5. Take Breaks to Get Refreshed

• This is not a critical programming tip, but a good tip for every hard worker out there.
• This is much easier said if you don't have any social responsibilities.
• I guess the gist here is to do what you need to do to work smarter and healthier.

6. Use Online Resources

• I thought I would see some reference here to StackOverflow or useful sites where programmers learn to "debug" and "troubleshoot", but I didn't. Thus, make sure you bookmark sites that help you not only learn to code, but learn to decode/encode (so to speak). :)
• There are hundreds of online tutorials. So, go through some sites, pick your top few, and be sure to add YouTube to that list. There are great channels on YouTube offering free tutorials and resources. Also, tech giants offering tutorials use YouTube. Note: I haven't seen many tutorials on Vimeo (or any other online video library site).

7. Read Relevant Material

• What's funny to me about this tip is that the statement with  the "majority of real-life situations...the client's team will possess complete knowledge of their business". From my experience, this is not really true. As a software developer, or aspiring software developer, you'll learn that the business experts eventually become outdated (due to lack of vision and improving current processes rather than focusing on disrupting processes for greater ROI) or they become dreamers (and provide unrealistic visions and predictions).
• Before becoming an expert in a business domain, you'll need to ask yourself about the direction that you want to take your work. Do you want to start your own business one day or invent something? Or, do you want to become a tech guru within the company or industry you're in? After you choose the question to answer (and you can't choose both), then you will learn to understand how to code in ways that will take you to your career destination.

8. Learn From the Bugs

• This is another tip which I find interesting to lack the advice on specifically leveraging online community forums. One particulary online forum that is picking up attention is GitHub. So much code is not being stored in GitHub that one can pick up lots of knowledge on how to create by leverage.
• Again, leverage sites like StackOverflow for debugging.
• Understand the limit of tools used for debugging as well.
• Better yet, learn to write tests (e.g. unit tests, end-to-end tests) before you write your program and then you'll pick up a better habit than debugging.

9. Never Get Tired of Practicing

• Practice with other like-minded coders.
• Practice to innovate, not just to improve - because you'll never reach perfection.
• Problems are neverending, and you'll need to discover how to become quicker at finding or creating solutions. This takes practice, too, and can be practiced outside of coding like with puzzles, understanding economic impact on local developments, studying psychology and quizzing behaviors, and learning different parts of society by volunteering and traveling.

10. Keep Your Cool

• I actually thought this tip would address the politics in a workplace. Every developer not only needs to know how to "play with others", know how to code according to customer satisfaction, know businees needs and where the development team fits in, but also how to challenge bad ideas without offending people as well as add value to an organization's mission.
• Never think your work life is about your life; it's about work. Never bring "work" to your life. Bring "life" to your work.

Good luck, newbie!

Technical Skills a Software Developer Needs

Devs,

Here's another great article I read today. I, for the most part, agree with this author.

https://simpleprogrammer.com/2016/07/18/technical-skills-software-developer/

And here's a bonus article: Why SmallTalk is great to know?
http://techbeacon.com/how-learning-smalltalk-can-make-you-better-developer

I can add that it's definitely good to know when having conversations with older techies. I remember one developer from my first job rave about how SmallTalk was THE language and the industries were wrong for jumping into the next "hyped" language.

And another one on the importance of the rising skill of "data analysis":
http://venturebeat.com/2016/07/17/forget-learning-to-code-every-employee-should-know-data-analysis/

Enjoy,
G2