Harri Lakkala retweeted
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: youtu.be/dHIppEqwi0g
• Spotify: open.spotify.com/episode/12d…
• Apple: podcasts.apple.com/us/podcas…
Brought to you by:
• @statsig — The unified platform for flags, analytics, experiments, and more. statsig.com/pragmatic
• @linear – The system for modern product development. linear.app/pragmatic?utm_sou…
Harri Lakkala retweeted
The post-re:Invent #AWS IAM updates just dropped:
awsiamdata.com/changelog?1
There are now more than 400 AWS services!
#awscommunity #reinvent
Harri Lakkala retweeted
How to decode the AWS account id from AWS key id
medium.com/@TalBeerySec/a-sh…
standing on the shoulders of giants: @0xdabbad00 @__steele
Harri Lakkala retweeted
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 retweeted
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 ➡️ goo.gle/3Rv7gWc
Harri Lakkala retweeted
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.
Harri Lakkala retweeted
If you are an individual contributor engineer, you really need to print this out and hang it somewhere. newsletter.pragmaticengineer…
Harri Lakkala retweeted
There’s this YouTube channel that releases maybe 1-2 videos per year but they are absolute bangers. It’s called KRAZAM and it’s the only one I set to get notifications for new videos.
If you work in tech, you might also find them funny & worth watching:
Harri Lakkala retweeted
AWS NLBs can now have security groups of their own.
Nuance: there are now two types of NLB: those *created* with SGs and those created without SGs. SGs can be changed for an NLB created with them, but you can’t add them to an NLB created without SGs.
aws.amazon.com/about-aws/wha…
Harri Lakkala retweeted
The Japanese multiplication method makes everybody feel "I wish they taught math like this in school."
It's not just a cute visual tool: it illuminates how and why long multiplication works.
Here is the full story.
Readers added context they thought people might want to know
現行の日本教育では、この掛け算の方法は教えていません。以前この方法が日本でもインド式掛け算と話題になっていました。実際はどこの国で教えられているのでしょうか?
nlab.itmedia.co.jp/nl/articles/14…
Current Japanese education does not teach this method of multiplication. This method was once talked about as Indian-style multiplication in Japan. Where is it actually taught?
nlab.itmedia.co.jp/nl/articles/14…
Harri Lakkala retweeted
I’ve been working with @awscloud’s #Bedrock service for a couple of months now at @caylentinc, and I’d like to share some of what I’ve learned. 🧵
Harri Lakkala retweeted
The Amazon Builders' Library is an hidden gem: it consists of articles written by some of the most senior AWS engineers covering foundational patterns and principles used when building AWS services.
Most learnings can be applied anywhere. Here are my favourite articles:
Harri Lakkala retweeted

Min Choi@minchoi23 Jun 2023
United States
United StatesConnected via United States App StoreAccount-level information, not a live location or per-post device.
Midjourney v5.2 just dropped with "Zoom Out" feature
And people are already creating insane images
Here are 10 mind blowing examples:
Harri Lakkala retweeted
The AWS CLI (v2.12.0+) can be used to create a tunnel to connect to RDS DBs now, but I created a tool that tries to make it more convenient.
1. Create EIC endpoint
2. Download tool
3. Run `rdsconn p`
4. Run `psql -h 127.0.0.1 ...`
github.com/aidansteele/rdsco…
Harri Lakkala retweeted
Andrej Karpathy is a legendary AI researcher who helped start OpenAI.
He recently gave a talk on how to craft great GPT prompts that almost everyone missed.
I watched the 40 min talk - here's @karpathy's top 5 tips to make AI work better for you:
Harri Lakkala retweeted
Super Heavy’s engine shielding is quite an impressive system, and Elon Musk has been talking a lot about this with Booster 9. Let’s take a closer look at how SpaceX isolates and protects all 33 engines on the Booster. (1/14)
📸 @CosmicalChief
Animations provided by @ChameleonCir
Harri Lakkala retweeted
I published a blog post (and PoC CLI) describing how the new Systems Manager Default Host Management Configuration (what a mouthful) provides a new way to pass an IAM role to all EC2 instances in your account+region - even those without instance profiles.
awsteele.com/blog/2023/02/20…
Harri Lakkala retweeted
AWS just released mountpoint - an open ssource high-throughput file client for S3. Written in Rust!
github.com/awslabs/mountpoin…
Harri Lakkala retweeted
ok, after many tests, I've managed to get my Additive Prompting structure working for interior design/architecture photography with 90%+ coherence to the prompt in Midjourney.
Examples & prompts in thread. Read them as you look at the images
🧵 Thread
Harri Lakkala retweeted
If you could infect any image on AWS ECR Public Gallery, which one would you choose? 👀
blog.lightspin.io/aws-ecr-pu…



























