Commentary 1:

Based on the reading "How Differential Privacy Enhances Microsoft's Privacy and Security Tools: SmartNoise Early Adopter Acceleration Program"

1) Affect on Past Work or Internship:

During my previous Software Developer Internship at Elakk Technologies, the ideas and technologies proposed in the blog would have significantly impacted my work. During my internship, one of the biggest challenges I faced was working with sensitive data while ensuring that individual privacy was protected. The introduction of differential privacy as a tool for safeguarding privacy would have made my job much easier and more effective. By applying differential privacy to our datasets, we could have extracted useful insights while ensuring that individual privacy was protected.

The addition of Azure Confidential Computing would have also been a valuable tool in my previous internship. One of the biggest concerns when working with sensitive data is the risk of insider attacks or malicious administrators. By using Azure Confidential Computing, we could have reduced the risk of these types of threats and ensured that our data was secure throughout its life cycle.

2) Impact on Current Work or Internship:

In my current job/internship, the ideas and technologies proposed in the blog post would also have a significant impact. As data continues to play an increasingly important role in driving innovation, it is crucial to ensure that data is secure and private throughout its lifecycle. The use of differential privacy and other technologies would allow me to work with larger and more complex datasets, while still ensuring that individual privacy is protected.

Furthermore, the SmartNoise Early Adopter Acceleration Program would provide an opportunity to engage in technical and conceptual considerations incorporating SmartNoise and differential privacy into solutions. This would allow me to gain a better understanding of how these technologies can be applied in real-world scenarios, and how they can be integrated into existing systems.

Overall, the ideas and technologies proposed in the blog post have the potential to greatly impact the work of software developers, particularly those working with sensitive data. By providing stronger protections against threats and ensuring individual privacy, these technologies can enable developers to extract more useful insights from datasets and drive innovation more securely and responsibly.

3) Affect on Future Work or Internship:

The impact of these ideas, concepts, and technologies on my future job or internship will depend on the specific role and industry. However, I believe that the need for strong security and privacy protections will only continue to grow in importance. As more organizations collect and analyze large amounts of data, the need for tools like differential privacy and Azure Confidential Computing will become even more critical. As a Software Developer, it will be important for me to stay up to date on the latest developments in this area and to incorporate these technologies into my work where appropriate. I believe that the ideas, concepts, and technologies proposed in the blog have the potential to revolutionize the way we work with data and ensure that individual privacy is protected. As a Software Developer, I am excited about the possibilities that these technologies offer and look forward to incorporating them into my work in the future.

In conclusion, the ideas proposed in the blog have significant implications for my professional experiences as a software developer intern. The concept of differential privacy, the use of cloud computing and AI, and the SmartNoise Early Adopter Acceleration Program are all exciting developments that I am looking forward to exploring. By gaining experience in working with these cutting-edge technologies, I will be better equipped to navigate the changing landscape of data privacy, security and to develop innovative solutions that benefit society.

Commentary 2:

I really enjoyed the mindset discussion of Stefan Gross-Selbeck's TED talk "Business model innovation: beating yourself at your own game" and his walk through of what mindsets are important and why.

I have not really put a lot of thought into why I operate very differently than my peers here at ASU but this would seem to explain a lot of it. I act like I am at a start up and have been fortunate enough to have good leadership and insulation to operate safely and effectively in this manner. While I say I come from a corporate background it is an unusual one. I was at AOL before we hit 10 million members and I came back after we bought Time Warner. That was two very different companies. Before we bought Time Warner, we behaved like a startup.

We had an attacker mindset. We were constantly and intentionally disruptive to ourselves. It wasn't about being disruptive to us. It was about us all having all this new cool technology and things we could do with it and we just wanted to do more. "We" didn't add gaming to AOL because it would make money, it was free for years inside the service, we did it because we wanted to play online games. Most of the disruptive innovation in the early days at AOL were because of a love and passion for what we were accomplishing so we never really thought about it being disruptive. When we needed a new web browser we made our own, twice, really three times. The GNN one was pretty damn good. We were killing moving to the web (getting ready of the AOL software piece) before anyone was and then our shift went from start up mode to corporate and it all came crashing down.

We were agile when the word actually meant something. We shifted and changed directions so often that summaries weren't often that important. It was more of a "where are we now?" status updates without explanations of how we got there. We did not have good processes yet, or maybe ever, but we were nimble and able to adjust easily. This made support teams look like miracle workers and definitely lead to a poor cultural situation where we began to value those quick problem solvers as heroes. This probably set good QA work back 20 years. Hero culture made quality less important. I didn't see that begin to change until around 2010 or so. Getting quality assurance concerns as a first though rather than a last though is still a problem but it happens now more than I have ever seen before. Its built into DevOps, we beg both Dev and Ops to care. Being agile was better than being right or sometimes even functional.

Which that goes right along with Stefan's last mindset, failure is OK. We did that a lot. We failed daily and it was often encouraged. We used to use the phrase "throw sit against the wall and see what sticks" as if it was a business process. I miss those days, but it the internet was a fun place. Technology was not there to run businesses, it was there to make us relax and enjoy something not so - well not so whatever it is now. The ubiquity of the technology has stolen much of its novelty charm and magic in many instances.

Answer the following Questions:

1) With respect to commentary 2, did the commentary focus on the application of the concepts/frameworks discussed in the readings to current or prior work environment(s) and did they address things from their professional (past, present, future) perspective? Or did they lean in too much to their personal perspectives or opinions on the matter?

2) From commentary 1 perspective, tell if commentary 2 relates to commentary 1. Where do they have a common ground? Where do they disagree?

3) From commentary 1 perspective, tell if commentary 2 changed your perspective in any way. If so, how? If not, why?