Hey!
Summary of this email:
- All Spark courses published in the Standard plan!
- How a senior dev does vibe coding
- What's happening next week?
Estimated reading time: 1 minute.
🚀 All Spark courses published in the Standard plan!
Spark is a distributed processing engine widely used in Big Data projects for working with large volumes of data efficiently.
We know our audience is more 100% development-oriented, but we think this is a very relevant topic because, as a role, we're taking on more and more responsibilities. Full-stack keeps getting more full.
That's why we wanted to create this course series with Christian Herrera, Senior Data Engineer at Adevinta, who has battled with Spark in production with millions of records for many years.
With the Spark: Best Practices and Deployment course just published in the Standard plan, all 3 are now available there:
- Spark for developers: Learn to go from data to decisions using Apache Spark. 100% focused on devs.
- Spark Integration with Kafka, Rabbit and SQS: Integrate Spark with queue systems to improve scalability.
- Spark Best Practices and Deployment: Take Spark to production following best practices and avoiding common mistakes.
💻 How a senior dev does vibe coding
Vibe coding is a relatively recent term (first quarter of this year), but it feels like we've been using it for years.
It consists of developing code without looking at it, using AI 100%.
This concept was born as a tool for people without technical knowledge to be able to develop, but it quickly got tainted by the code it ended up generating:
- Major security holes: Many databases were left exposed.
- Code that didn't scale: Applications crashed with just 10 concurrent users.
- Massive server costs: Deploying without understanding how everything worked underneath, many applications racked up server bills in the thousands of euros.
- At some point, adding new features broke existing ones: All because the code was super coupled.
With all of this, a somewhat negative image of the concept has emerged, but...
What happens if a very top senior dev starts vibe coding?
Summary: They mitigate all those errors by having a "human in the loop" who has control over everything.
Last Tuesday we interviewed Alfredo Artiles, co-founder and CTO of Audiense, a programmer with nearly 20 years of experience, to tell us how he built an application with 100% vibe coding while on vacation at the beach. You can watch the live stream here.
🤷 What's happening next week?
In next week's newsletter we'll be announcing some things. Updates that we believe are very relevant for the Codely world. Don't miss it. 🤞
And since you've made it this far in the newsletter, here's the joke of the week, which I know you were waiting for:
> When is the best time to talk about containers? DockerWhenever you want. 😂
Cheers!