Harri Lakkala

Cloud engineer/architect, gadget freak, and dad - Entusiastic about all things D(igital)

[Harri Lakkala @hrry]

Full house at the #AWSUserGroupTampere May meetup tonight. Big thanks to Gofore for hosting us at their offices! On the agenda 2 presentations: 1) AWS CDK open source project and 2) SOK's AWS Account Factory for Terraform migration. Happy to see the community coming together!

[Harri Lakkala @hrry]

@GunnarGrosch Looks like you have been busy, Gunnar! Any online version of your talk by chance? :) Would be interesting to see it.

[Gergely Orosz @GergelyOrosz]

Why does "vibe coding" not lead to anything productive, for the most part? A great person to answer is @addyosmani: he has been working on Chrome for 10+ years, and has just published his new book: Beyond Vibe Coding.

Watch or listen:

• YouTube: https://t.co/VbjHwunvwP

• Spotify: https://t.co/icIrSGADZ7

• Apple: https://t.co/q0TiDoazY3

Brought to you by:

•⁠ @statsig ⁠ — ⁠ The unified platform for flags, analytics, experiments, and more. https://t.co/ZCSOIcWv31

•⁠ @linear – The system for modern product development. https://t.co/si9FpjGgvH

[Harri Lakkala @hrry]

The second presentation for the #AWSUserGroupTampere comes from Antti Laiti (Exove) and handles using production data in development. Looks like we will cover a lot of storage services and tools, so it should be interesting.

[Harri Lakkala @hrry]

The best and smartest office pods come from Framery, and tonight the #AWSUserGroupTampere audience is hearing how they manage their DataOps with a small team (speaker Niko Laaksonen). Also, big thanks to Framery for hosting us tonight!

[Harri Lakkala @hrry]

We're kicking off #AWSUserGroupTampere Spring season with a meetup at Knowit's office. Jali Pieskä is our first presenter and he's sharing learnings about FinOps (cloud cost optimisation). Later on we'll also hear about the biggest AWS re:Invent launches from Aki Ristkari.

[Harri Lakkala @hrry]

And our second AWS User Group Tampere talk is by Aleksi Häkli and it's titled "Peeling the onion". Aleksi will talk about planning cloud solutions and cloud migrations, so should be interesting. #AWSUserGroupTampere #AWSUGTampere

[Harri Lakkala @hrry]

Tune into our AWS meetup at https://t.co/mBMmcAlSjR. Massimo Prencipe is opening the evening talking about SBOMs (Software Bill of Materials). #AWSUserGroupTampere #AWSUGTampere

[Harri Lakkala @hrry]

AWS User Group Tampere meetup (hosted by Gofore) tonight is actually a workshop in Generative AI. First an introduction to GenAI on AWS by Joona Gynther (Solutions Architect at AWS) and then we'll be building an actual application using AWS Bedrock.
#AWSUserGroupTampere

[Tobias Müller @TobiM]

The post-re:Invent #AWS IAM updates just dropped:

https://t.co/BsLmyjn7HT

There are now more than 400 AWS services!

#awscommunity #reinvent

[Harri Lakkala @hrry]

This year I'm heading to AWS #reinvent2023 in person, and this will be my first time participating in in real life. Yikes! :D

If you want a quirkier coverage on the event, check out Corey Quinn's @QuinnyPig's re:Quinnvent at https://t.co/ziDWkvIKFh

[Harri Lakkala @hrry]

Our last presentation for the evening is now being delivered by Ari Palo – Lead Technologist at Alma Media, titled "Managing configuration(s) with AWS CDK". #AWSUserGroupTampere

[Harri Lakkala @hrry]

And now for something a bit different – a panel connecting cloud experts and product owners. "AWS Tampere Meets: Product Owners" panel hosted by Ben Matthews with Miro Nieminen (Framery), Manu Karppelin (HappyOrNot) & Juho Fröjd (Paytrail) in the hotseat. #AWSUserGroupTampere

[Harri Lakkala @hrry]

We're live again with #AWSUserGroupTampere. October meetup just kicked off with Jose Juhala talking about Connecting and automating AWS networks. Check our meetup event comments (https://t.co/je18TuHoeJ) for the live streaming links!

[Tal Be'ery @TalBeerySec]

How to decode the AWS account id from AWS key id
https://t.co/Q0URWCjIch
standing on the shoulders of giants: @0xdabbad00 @__steele

[daniel:// stenberg:// @bagder]

We are cutting the release cycle short and will release curl 8.4.0 on October 11, including a fix for a severity HIGH CVE. Buckle up.

[Harri Lakkala @hrry]

Kicking off the #AWSUserGroupTampere Autumn season with a meetup hosted at the Reaktor innovations offices in Kehräsaari. First presenter Pekka Malmirae from Nordhero talking about Mastering AWS deployments with Terraform & Terragrunt.

[Google Cloud Nordics @GoogleCloudNord]

Now the #GoogleCloudSummitNordics keynote is over, the breakout sessions begin!

Which session are you most looking forward to today? 🚀 Take a look at the full agenda here ➡️ https://t.co/98N0pDPsxN

[Santiago @svpino]

Software estimates are one of the oldest lies we tell ourselves.

We all know they don't work, but pretend they mean something and later feel enraged when shit hits the fan.

I focused a big part of my undergrad on software estimation.

After graduating, I wrote plenty about the topic.

Then, I started working for a company where I spent years researching how to make better estimates. We sold multiple millions of dollars of software using the tools I built.

I read everything there's to read. I could recite Steve McConnel's "Software Estimation" book from top to bottom.

Here is the most important lesson I learned:

People can't estimate software. It doesn't matter who they are or how much experience they have.

Estimating software reliably is science fiction.

And the best part:

They will ask you to estimate something. They will tell you they understand it's not exact. They will promise they won't hold you accountable.

And then they will. They always do.

There are two solutions for this. Let's start with my recommendations for those who don't have a choice:

1. Remove "quick," "simple," "straightforward," "easy," and every similar word from your dictionary. Never use them. Don't let others use them when referring to your work.

2. Never volunteer an estimate. Everything you say will be used against you.

3. When forced, estimate work you know you can complete today. Always estimate with a range: "It will take me 2 - 4 hours."

4. Estimate anything you won't do today in days and weeks. Say, "I should finish that feature sometime this week." Do not estimate future work in hours.

But we all know your manager will force you to give an estimate. Here is what you should do:

1. Estimate how long you think it will take you to complete the task.

2. Multiply the number by 3. This will be the lower range of your estimate.

3. Double the lower range of the estimate. This will be the upper range.

Example: If you think something will take you 1 day of work, say "between 3 and 6 days."

Here is the funny part:

It won't take you between 3 - 6 days. This is as much bullshit as any other method you can think of.

The true solution for this problem:

Work for a company that doesn't care about estimates.

[Jaana Dogan ヤナ ドガン @rakyll]

If you are an individual contributor engineer, you really need to print this out and hang it somewhere. https://t.co/noESiuF7IZ