IT 2.0

I had Backlog.md on my radar for a while, but I never ended up using it.

This blog post assumes you are somewhat familiar with Kiro specs driven development (if you are not, this is a great read) and the Ralph Wiggum loop (if you are not, this is another great read).

This is a short and unstructured blog post on some experiments I have been running using Kiro spec-driven development.

The world is changing.

In this post, I am continuing my Kiro experiments to produce better specs outcomes.

Many of us have one or more litmus tests for assessing the capabilities and workflows of generative AI code assistants.

At re:Invent 2024 the Amazon Q Developer team has introduced a number of additional capabilities.

The CloudFormation team has been on a roll in the last 12 months.

It's pretty clear (to me) that Generative AI assistants users are coming to expect a certain level of personalization to their needs.

Amazon Q Developer is what pays my bill and the generative AI-based code assistant I use more regularly.

Last week I was in Istanbul for the local Community Day, where I talked about Generative AI assistants (e.g.

I have long been saying that generative AI english-to-code capabilities (that is, the ability for an assistant to produce code based on a prompt) are overrated - but very useful - while the code-to-english generative AI capabilities (that is, the ability…

If you have been deep into generative AI, you probably heard about the notion of "prompt engineering".

Last week Darren Shepherd, CTO at Acorn, announced on Twitter his last crazy OSS project: GPTscript.

The original title of this blog post was "Building a Generative AI application to fight WhatsApp vocal messages".

I have worked in IT for almost 30 years and I have experienced first-hand tectonic shifts in this industry.

In the last few months, the "generative AI" discussions have been dominated by LLMs (or Large Language Models).

I spent the last 30-ish years of my professional life working on what I generally refer to as "compute systems abstractions".

In the last few months, I have talked to a couple of Beanstalk customers that wanted to explore ways to modernize their deployments.

I know, I am boring.

In (virtual) part 1 of this blog post (yes it has a different title) I have shown how to use a combination of AWS Step Functions and Amazon EventBridge to modify the behaviour of Amazon ECS and virtually adding a new feature that doesn't exist in the prod…

In an effort to dive deeper into event driven architectures, I have lately been experimenting with AWS Step Functions as I have documented in this blog post where I have refactored the application logic of my demo application Yelb into a set of state mach…

Code is a liability.

Yelb is the demo application I use to experiment with and learn technologies.

I have lately invested a lot of time keeping an eye on StackOverflow because there is a ton to learn in terms of how AWS customers are using our products.

Part of my job at AWS is to explore the art of possible.

A few weeks ago I have published an AWS Fargate related project in GitHub called Fargatecount.

This article was originally posted on the AWS compute blog.

A few days ago, at Incontro DevOps Italia (IDI) 2019 I did a breakout session about the topic in subject.

At Amazon we work backwards from customer needs and this is embodied in everything we do.

When I joined AWS last year, I was trying to find a way to explain, in the easiest way possible, all the options the platform offers to our users from a compute perspective.

As you may have heard, late last year I joined Amazon Web Services.

This is my first blog post as an AWS employee.

I have an awesome job, an awesome manager and I work for one of the best companies around.

Introduction VMware, Amazon Web Services and Microsoft are in the middle of some interesting technology and services roll out that have the potential of moving the needle in cloud adoption (spoiler alert: whatever cloud means).

Yesterday I noted a tweet from Frank Denneman: I guess he was asking this in the context of the VMWonAWS cloud offering and how, with said service, you could provision vSphere capacity without having to “acquire server hardware”.

Another pet project I have spent cycles on as of late is an open source sample application called Yelb (thanks to my partner in crime chief developer Andrea Siviero for initiating me to the mysteries of Angular2).

This article was originally posted on the VMware Cloud Native corporate blog.

I have lately started a tradition of copying/pasting reports of events I attend for the community to be able to read them.

Following the establishing best practices of ‘open sourcing’ my trip reports of conferences I attend, I am copying and pasting hereafter my raw comments related to the recent Kubecon EMEA 2017 trip.

This articlewas originally posted on theVMware Cloud Native corporate blog.

In the second half of 2016 I had an opportunity to focus (almost) exclusively on vSphere Integrated Containers all the way through its GA in early December.

In the last few months I have been looking at Rancher (an open source container management product) as a way to learn more about Docker containers and understand better the ecosystem around them.

A few weeks ago I shared on my blog a cleaned up conference report from Serverlessconf 2016.

Warning: social media experiment ahead.

Serverless computing is the new buzzword.

This is going to be a short and (somewhat) visual blog post where I want to discuss the absolute madness that is going on in “container land” (for lack of a better characterization).

Yesterday I bumped into a semi-draft of code I wrote a while back and that I have never checked in into GitHub.

No doubt there is an explosion of complexity these days in IT.

This article was originally posted on the VMware Cloud Native corporate blog.