Review: Microsoft Open Source Stories - Starting the .NET Open Source Revolution

I really appreciate the author (and his reference to the other authors) on telling this story (and continuing to tell the story of open source revolution).

Quite interesting to see how legal teams slow down tech teams. Even more interesting that legal teams seem to work more independent unlike many tech teams that work more interdependent (because no one likes to re-invent the wheel). Someone's going to need to change the legal system. Well, at least for the tech industry.

https://medium.com/microsoft-open-source-stories/starting-the-net-open-source-revolution-e0268b02ac8a

Journey into SET: No WebElement.isClicked()

In creating the Test Framework using Selenium for testing a specific web application, I am sort of shocked that the authors of Selenium would allow a WebElement to be "clicked" but not keep track whether this WebElement "isClicked" or even "isClickable".

https://seleniumhq.github.io/selenium/docs/api/java/org/openqa/selenium/WebElement.html#click--

So, anyhow, learned the hard way and had to really pay attention to reading the large paragraph in the API's method definition when it should the method should hanlde such cases or the Object should allow for handling such cases.

But, there's my issue too - why am I not contributing to this open source library set (tool)?

I need to get my game up and contribute, not complain.

I got around my problem and solved using the:
driver.navigate.refresh()

Well, at least I now know. :D

Review: Microsoft changed the way they Interview

This is great to finally hear! Not because I can't pass such technical difficult interviews, but because such in-depth technical interviews do not reflect how people actually work in tech environments. There's a lot more to developing a key product pushing the industry's tech edge than a random research conclusion or unrealistic (useless) technical solution.

The "Alternative Interview Framework"
https://blog.usejournal.com/rethinking-how-we-interview-in-microsofts-developer-division-8f404cfd075a

P.S. French is a very useful language in the tech world, as I'm starting to see.

References

• https://www.businessinsider.fr/us/microsoft-new-developer-interview-process-2018-12
• https://www.businessinsider.com/how-google-hires-2013-6

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: Exploratory vs Manual Testing

@fwmoyer states the difference between Exploratory Testing and Manual Testing is a mindset. And I agree with him. Here's a quick article on explaining why.

https://www.softwaretestinghelp.com/exploratory-testing-vs-scripted-testing/

Overall, context is always valuable when driving something purposeful. In order to reach quality results (i.e. results that matter and add value), context is required especially to help to create productive roadmaps whether designing, developing, and/or testing.

Review: Jamboard (by Google)

I don't know why I'm just now hearing and learning about Google's Jamboard, but I am glad to hear about it now than later.

One of the benefits of this product is its mobility. You can do a lot with this tool like with a smartboard, but you can move it around. Here's an example of why being "mobile" is superb. What if I'm innovating well at work but for some reason I get laid off? Well, I can take my Jamboard and ideas with me. That's it. Well, and continue my career. :D

One of the biggest disadvantages in growing ones career is having to start over. In today's world where there are many smart people making many smart moves, a person needs to have smart tools that move with them as well. So, this is my pitch for this tool by Google: Jamboard.

Check it out.
https://www.youtube.com/watch?v=gXwV5SlKLAE (intro to Jamboard)
https://www.youtube.com/watch?v=hVZPh8Zz8lw (intro to Jamboard in 'Google for Eduction')

Review: Traditional Developer vs Cloud Developer

Another interesting article.
https://blog.bluesoftglobal.com/cloud-developer/

I need to do more research on the argument made in this article about the need to become a Cloud Developer. There will just be too much technology to learn if we keep thinking that a techie needs to learn stack development, deployment, tech support, translation of business domain knowledge into technical feasibility, and more.

Teams will continue to grow and not with an all-in-one talented techie. Developers will continue to need to specialize, in my opinion. But, if the cloud handles all the deployment and support issues, then maybe a developer can just focus on - developing?