More. Better.

Mario Munoz

What would it look like to be a good software engineer? Would it mean that you are able to solve complex problems with proven solutions? Or would it mean that you can provide novel and creative ways to solve hard problems? The introduction of AI tooling into a developer's workflow promises gains in productivity. But what does that mean? More code? Better Code? Less toil? More time?

Some executives bullish on this technology claim that AI assistants will eventually shorten workers' work weeks. However, the likeliest scenario is not a shorter work week, but increased demands within the same time constraints.

How do we become better engineers within the current climate of overhyped AI technologies?

About Mario Munoz

In my past lives, I've enjoyed playing guitar and bass, kicking a soccer ball, or playing an occasional video game. In my career, I've been an editor at a non-profit, taught as a pre-school teacher, managed payroll for a professional baseball team, and worked as an analyst/project manager for HR systems. More recently, I've been working as a software engineer for a company called BCM One.

I also code Python by night, which is what happens when there's not enough time during the day to poke around and break things. In the past couple of years, I've presented several talks/tutorials at PyCon US, DjangoCon US, Python Web Conference, North Bay Python, PyGotham, PyOhio, and others. Sometimes I neglect/blog on my website Python By Night, and start (or abandon) too many side projects.