I am working on creating an Even Driven Architecture framework for Kotlin.
I went through the Software Architecture Patterns for Serverless Systems book, which I think it is fantastic. I learned a lot but I still had a lot of doubts to actually use the ideas in real life. So I started dissecting the companion framework, which is in written in Typescript. I have been going piece by piece and converting to Kotlin which I think it is more expressive (and fun) and it is allowing me to understand how everything fits together.
Eighteen years here. I am not American but I think this is a holiday that we can all celebrate as reminder that we should be grateful for what and specially for who we have, independently what we don't have.
I do agree that you should be able to fix most bugs in 2 days or less. If you have many bugs taking longer to fix, it may be an indication that you may have systemic issues. (e.g design, architectural, tooling, environment access, test infrastructure, etc)
True. Adding to these. Perl6/Raku suffered from the second system effect. Described in the Mythical Man Month. Larry and company were over confident with their previous success.
I know that there are many reasons for people to work after 65. I also know that sometimes life takes surprising turns. But it makes me nervous to see people so capable as Dave that are well known in our industry looking for a job. What is the hope of the rest of us ? I love software engineering but I still hope to be able to retire to work on my own projects.
Similarly in software. When a software product is well crafted/engineered, it has less defects, it is easier to understand and modify, saving a lot of time and effort. I do not see that anymore. I see a lot of smart young engineers but they are managed in a way in which the craft doesn't matter and what matters is how many story points you do.
I don't disagree, but I have seen a few counter examples in my life.
Some of the smartest people that I have known are also the kindest. It is like they are so smart that are able to understand and empathize with other people thoughts and feelings. In any place I go, I look for the kindest people and frequently you also find they are also really smart and interesting.
TUI were great for many business applications, specially those in warehouses or factories. They were easier to write and modify. Many business applications were migrated to web for little gain. IMHO.
True. A lot of work done in big companies is waste.
6. A lot of unneeded complexity is added.
Perhaps if we can only use AI to understand the wasted effort.
Also, I rather have the ICs with some slack and time for clear thinking to address the big issues than always be busy on a mountain of work that goes now where.
I agree that a lot of software will be done declaratively rather than imperatively. But we will create DSLs for that. I don't think we will use math for that. And somebody needs to create the DSLs.
I understand this point of view is contrary to popular opinion. The justification of microservices is to allow a team of let's say 10 developers to scale to 100. What you do is create 12 teams of 8. Each team owns their microservice with well defined APIs, and are allowed some flexibility on languages, tools, process, etc. Of course, it is a good idea to leverage common tools and such, but not obligatory.
Commonly we see a team of 20 maintaining 40 microservices, which becomes very difficult to manage and provides little gains. IMHO, this si the wrong approach. Microservices are tiny from the point of view of Netflix, or Amazon.
That is the whole purpose of doing microservices. Every team can operate independently. Choose their tools, processes, etc. As long as they respect their API Contracts.
I went through the Software Architecture Patterns for Serverless Systems book, which I think it is fantastic. I learned a lot but I still had a lot of doubts to actually use the ideas in real life. So I started dissecting the companion framework, which is in written in Typescript. I have been going piece by piece and converting to Kotlin which I think it is more expressive (and fun) and it is allowing me to understand how everything fits together.
Typescript framework: https://github.com/jgilbert01/aws-lambda-stream