Article Review: Best Practices for Naming Variables

This is a good conversation to have with any development team. 

Strangely, I didn't see any comments from product managers or folks who give developers requirements to build a product. Often, developers try to align the words used for variables and functions to the words used in requirements. I would like the academic research to consider the business aspect.

https://thenewstack.io/best-practices-for-naming-variables-what-the-research-shows/

Meta "Zuck Bucks" over Cryptocurrency

While the cryptocurrency industry continues to struggle for its "worth", I think the virtual reality world may have a quicker breakthrough into shifting the currency exchange systems and personal transactions. By taking Meta for instance, if Meta establishes rules that are aligned with the real world systems, then people will more likely make exchanges in Meta world especially upon initial meetings. This is something to watch.

https://arstechnica.com/tech-policy/2022/04/project-zuck-bucks-meta-plans-virtual-coin-after-cryptocurrency-flop/

6 Best Practices for API Design (and One Tool) by AWS Werner Vogel

 I really like these 6 Rules by Chief Technology Officer (CTO) "Dr. Werner Vogel" of Amazon Web Services (AWS):

1. APIs are Forever
2. Never Break Backward Compatibility
3. Work Backwards from Customer Use Cases
4. Create APIs That are Self Describing and Have a Clear, Specific Purpose
5. Create APIs with Explicit and Well-Documented Failure Modes
6. Avoid Leaking Implementation Details at All Costs

For details, read this article - https://thenewstack.io/werner-vogels-6-rules-for-good-api-design/

Or, watch his video -

Chrome Dev Summit - Recaps

 I finally got a chance to read (watch) the Google Chrome Summit videos. Very insightful!

Summit Recaps

• https://developer.chrome.com/devsummit/

Useful Links

• https://developer.chrome.com/docs/privacy-sandbox/overview/
• https://privacysandbox.com/

Related Links

• https://privacytools.seas.harvard.edu/

White-collar programmers & Blue-collar programmers are both necessary

Found this article by Mike Loukides to have great points on the future of programming, but even more on the future of the workforce. After all, people need work in order to live. Particularly, I like his terms and definitions of "white-collar programmers" and "blue-collar programmers".

https://devops.com/rethinking-programmer-education-for-todays-coders/

Microsoft's VS Code now in the "Cloud"

I'm really excited about the progress Microsoft has made especially with adding VS Code into the "cloud" for development. There are lots of reasons why I am happy about VS Code, but the top reason is the need for local space for my personal media and content (which means less space for installing tools and IDEs). Plus, the ability to work anywhere (with a browser), anytime, makes "work remotely" even a bigger benefit. Of course, this comes with the strong assumption that one can access the Internet and the network has high bandwidth and speed.

https://vscode.dev (start playing now)

Read more about this @ code.visualstudio.com/blog

Quick Refresher: Functional Programming vs Imperative (Procedural) Programming

Hey! It's been a while, and I'm just posting this real quick and then back to learning. (I have a steep learning curve ahead of me in order to catch up from being stuck in the new dark ages of coding. Blah.)

Functional programming vs Imperative programming

I have not heard of this term "imperative programming" until I started learning more about the the Reactive Programming. So, I looked it up and found this nice article by Microsoft providing a brief explanation:

https://docs.microsoft.com/en-us/dotnet/standard/linq/functional-vs-imperative-programming

Also, Microsoft's Ignite (online conference) is coming up soon!

https://myignite.microsoft.com/home

Cheers!