GPT Store, Cloud, DDD and more
Our engineers hand-picked content for you to stay updated with the IT world. Recommended by both technical and non-technical leaders.

GPT Store, Cloud, DDD and more

News

The first stable release of OpenTofu, an open-source fork of Terraform, is now available, marking a significant milestone with new features and enhancements for improved infrastructure management.

OpenTofu's roadmap includes maintaining compatibility with Terraform and introducing new features like client-side state encryption, showcasing a balance between innovation and user-centric development. OpenTofu's development has been significantly shaped by its active community, with contributions from nearly 60 members.


OpenAI launches the GPT Store, offering ChatGPT Plus, Team, and Enterprise users access to over 3 million custom ChatGPTs. The store includes a variety of GPTs for different uses, like writing and coding.

A monetization program for GPT builders is planned, rewarding user engagement. Team and Enterprise plans offer enhanced admin controls for GPT management, prioritizing security and compliance.



Industry

In this text, Gergely Orosz examines the impact of changes to Section 174 of the US tax law, particularly on bootstrapped software companies. These changes, effective from 2022, require companies to amortize software development costs, including labor, over five to fifteen years, instead of expensing them immediately. This shift has led to unexpectedly high tax bills for many companies, particularly affecting small and medium-sized businesses.?

The article highlights the challenges these businesses face, such as potential layoffs or reduced hiring of software engineers, and discusses the broader implications for the US tech industry, including reduced competitiveness and a potential shift in where companies choose to incorporate or hire developers. It also delves into the background of Section 174, part of the 2017 Tax Cuts & Jobs Act, and its unintended permanence due to failed negotiations in Congress. While large tech companies like Microsoft and Netflix have managed the additional tax burden, the impact is more pronounced on smaller companies with tighter cash flows.?



Engineering

  • Sebastian Gebski 's article offers a detailed critique of Domain-Driven Design (DDD), focusing on its role in managing complexity in software development. Sebastian acknowledges DDD's strengths in modeling and the introduction of concepts like Ubiquitous Language and EventStorming, but points out its shortcomings in providing concrete guidance for evaluating and structuring models. His analysis suggests that while DDD underscores the importance of modeling, it lacks practical tools and frameworks for effectively assessing and organizing these models.

The article proposes that DDD could be improved by integrating elements from promise theory, methods for addressing coupling versus cohesion, and semantic analysis. This, as author argues, would offer a more structured and practical approach to tackling the real-world challenges of organizing and structuring models in software development.


Forrest Brazeal 's article delves into the debate over cloud computing, focusing on David Heinemeier Hansson (DHH), the creator of Ruby on Rails and a notable figure in tech.? Brazeal presents DHH's perspective that for many established companies, the cloud's benefits are overhyped and its costs, exorbitant. DHH recently made news by moving his company, 37signals, away from Amazon Web Services to an in-house data center, expecting significant cost savings.

Brazeal expands this discussion by introducing a "Cloud or Data Center?" matrix to evaluate different business scenarios based on IT competence and growth potential. He suggests that while some companies might benefit from on-premise data centers, others, especially those with lower IT competence or higher growth goals, might still find the cloud more advantageous. Brazeal cautions against romanticizing the pre-cloud era, reminding readers of the inefficiencies and challenges that cloud services have helped mitigate. He concludes that a shift back to data centers might bring back old problems despite the advancements brought by cloud technology.



Engineering Management

In the article, the focus is on contrasting two types of Service Level Indicators (SLIs) – Time-Based and Event-Based – used in monitoring service reliability. Time-Based SLIs measure the proportion of operational time a system functions correctly, offering intuitive and straightforward assessment but potentially misaligning with actual impact during uneven load periods. Event-Based SLIs, conversely, assess the ratio of successful events against total events, adapting more accurately to varying loads and providing a clearer representation of service impact. However, they can be complex in calculation and may quickly deplete the error budget during high-frequency bad events. The choice between these SLIs hinges on the specific needs of a service, whether reliability is gauged by operational time or event success, and the nature of the service's demand and traffic patterns.


The Impact Framework (IF) is an open-source tool that calculates the environmental impact of software applications, like carbon emissions, through a simple manifest file created by the user. It operates on a principle of composability, allowing for the integration of various custom or pre-existing models. Developed to address the challenge of quantifying the environmental effects of software across various components and platforms, IF provides a mechanism for detailed analysis, helping users to understand and potentially mitigate their software's environmental footprint.



Career?

Adrian Cockcroft ’s article discusses the challenges faced by companies transitioning from rapid growth to slower growth or shrinking, drawing from the author's experiences at Amazon and Sun Microsystems. It highlights that such transitions necessitate a fundamental shift in management and company culture, often leading to political maneuvering, reduced innovation, and increased micromanagement. The author suggests that companies in this situation have two viable options: make deep cuts early by shutting down entire product lines and removing management layers, or reduce salaries while offering new stock options.?

The author concludes by cautioning against joining companies that are no longer in a phase of rapid growth and are enforcing inflexible work policies. Instead, they recommend seeking opportunities in companies that are growing rapidly and have sensible work location policies, suggesting that such environments are more conducive to professional growth and innovation.



sign up button for the email version of newsletter
Do you prefer an email to read the news? Click this button and sign up for the email newsletter



Sebastian Gebski

Engineering Leadership

1 年

Apparently, the formatting has wiped the link to the DDD article :) Here you go: - part 1: https://no-kill-switch.ghost.io/the-failed-promise-of-domain-driven-design-part-1/ - part 2: https://no-kill-switch.ghost.io/the-failed-promise-of-domain-driven-design-part-2/ More to come (soon).

回复

要查看或添加评论,请登录

VirtusLab的更多文章

社区洞察

其他会员也浏览了