Nice notes and links.

Cristian Velazquez, a staff site reliability engineer at Uber, helped fix an important issue for the company's software in 2021. Then Uber asked him to write about it on the company's engineering blog. His post has generated over 84,000 page views since it was published.

Uber is one of several large companies hoping to reach engineers this way. Organizations like Google, Apple, and Meta are also in the blogging game.

The sites combine glimpses into what life is like at a company with case studies about complex programming tasks. The posts tend to have the titles of grad school papers and the editorial flair of instruction manuals. They're often created to increase transparency, provide resources to the engineering community — and entice people to go work at these companies.

Some companies' engineering feeds which I follow

• https://developers.googleblog.com/feeds/posts/default
• https://medium.com/feed/google-developer-experts
• https://aws.amazon.com/blogs/aws/feed
• https://developer.apple.com/news/rss/news.rss
• https://engineering.fb.com/feed/
• https://azurecomcdn.azureedge.net/en-us/blog/feed/
• https://building.nubank.com.br/feed/
• https://www.uber.com/blog/engineering/rss
• https://medium.com/feed/airbnb-engineering
• https://medium.com/feed/pinterest-engineering

Design Thinking could have really helped to understand the problem customers were facing (They were looking to to study new concepts, but moreover discuss ideas with their peers in class so interactive group learning).

Lean Startup would have helped to avoid the problem of building something people were not looking for (training without Powerpoint),

and Agile could have helped to cut the dev cycle with 50% by just building iteratively.

Gartner introduced a model in 2016 where they connected these three models.

Gartner: Combine Design Thinking, Lean Startup and Agile to Drive Digital Innovation

More information:

• https://www.productpizza.com/combining-design-thinking-with-lean-startup-and-agile/
• https://www.gartner.com/en/documents/3941917 (2019)
• https://www.gartner.com/en/documents/3200917 (2016)

Expand your horizons by trying out 12 different programming languages in 2023.

Go old-school with COBOL, cutting edge with Unison or esoteric with Prolog. Explore low-level code with Assembly, expressions with a Lisp or functional with Haskell!

More information:

• https://exercism.org/challenges/12in23
• https://forum.exercism.org/t/the-12in23-challenge/2213

Stakeholders’ buy-in and support is an integral component of success for any UX project, as they translate into resources, bandwidth, and approval. However, navigating stakeholder dynamics requires a thoughtful mix of listening, collaboration, communication, influence, and negotiation. This balancing act leads to stakeholder engagement and ultimately creates successful, long-term relationships.

Continuous communication with stakeholders is important for any UX project — first, because it helps them understand and appreciate what UX does and, second, because it helps UX learn about other essential aspects of the business. Despite this duality, the burden of communication usually falls on UX — because stakeholders are inherently busy and possibly focused on many other things besides UX.

DevSecOps is an engineering practice that promotes collaboration among development, security, and operations. When implemented, it creates a socio-technical system that uses automation for flexible, rapid, frequent delivery of secure infrastructure and software to production. Software development organizations must tailor each DevSecOps pipeline to the people, processes, and technology needed to provide a product or service. Until recently, there was no consistent basis for managing software-intensive development, cybersecurity, and operations in distributed systems.

Then in May, the SEI released version 1.0 of the DevSecOps PIM, a reusable reference architecture for DevSecOps pipelines. Software development organizations can use the online, interactive PIM as a reference architecture or assessment tool for their own DevSecOps pipelines.

More information:

• https://cmu-sei.github.io/DevSecOps-Model/
• https://insights.sei.cmu.edu/news/devsecops-platform-independent-model-receives-major-update/

In 2022, the SEI hosted the AAAI Spring Symposium on AI Engineering alongside co-organizers from Duke University, SRI International, and MIT Lincoln Lab. The symposium focused on human-centered, scalable, and robust and secure AI, with the goal of further evolving the state of the art; gathering lessons learned, best practices, workforce development needs; and fostering critical relationships. The papers in this collection were presented at the symposium.

More information:

• https://resources.sei.cmu.edu/library/asset-view.cfm?assetid=884163
• https://insights.sei.cmu.edu/news/symposium-delivers-new-perspectives-on-ai-engineering/
• https://resources.sei.cmu.edu/news-events/events/aaai/index.cfm

We introduce the challenges of DevSecOps philosophy and its applicability to the development and operation of trustworthy infrastructure-as-code, and we combine the solutions into a single framework covering all crucial steps. Finally, we discuss how the proposed framework addresses the challenges and introduce an initial design for it.

This special issue shows how the realm of infrastructure code has evolved to a status which—analyzed from a scientific perspective—can be considered mature, and rich in practices which can be seen as off-the-shelf approaches to continuous software engineering.

Software producing organizations face the challenges of changing demands, rapidly evolving technology, and a dynamic ecosystem in which their products and services need to operate. These challenges hinder software organizations being sustainable. The 5th International Workshop on Software-Intensive Business (IWSiB) brought researchers and practitioners together to discuss contributions within the emerging field of sustainable software businesses. The workshop was hosted by the 44th International Conference for Software Engineering. Birgit Penzenstadler's keynote on software-intensive business supporting resilience and sustainability for people, sparked the interest of the participating 30 researchers that continued to discuss 12 submissions.

The 4th International Workshop on Software Engineering Education for the Next Generation was held remotely on May 17, 2022. The workshop was part of the 44th International Conference on Software Engineering. It specifically supported the general theme of "Educating the Next Generation of Software Engineers". Building on its predecessors, the workshop used a highly interactive format, structured around eight short paper presentations to generate discussion topics, an activity to select the most interesting topics, and structured breakout sessions. This enabled the participants to discuss the most interesting topics in detail. Participants presented the results of the breakout sessions using mind maps.

This Guide spells out components of the software engineering discipline, promoting a consistent view of software engineering worldwide.

The newest version of the SWEBOK Guide includes new topic areas, updated topic descriptions, and the retirement of no longer relevant topics. Especially, agile (and DevOps) have been incorporated into many knowledge areas (KAs) since these models have been widely accepted since the last publication of SWEBOK. Three new knowledge areas (i.e., Software Architecture, Software Engineering Operations, and Software Security) guide foundational knowledge in software engineering. The new Guide will better integrate the related disciplines and rename and distribute some material into different knowledge areas. V4’s table of contents is shown in the following figure.

More information:

• https://www.computer.org/volunteering/boards-and-committees/professional-educational-activities/software-engineering-committee/swebok-evolution
• https://waseda.app.box.com/v/ieee-cs-swebok