@sandro_vol profile picture
Sandro Volpicella @sandro_vol
Joined December 2010
  • Posts 11,078
  • Following 901
  • Followers 7,323
1,709 Photos and videos
Pinned Post
Sandro Volpicella @sandro_vol
29 Aug 2024
The CloudWatch book is out! ๐ŸŽ‰ If you want to learn CloudWatch with a real-world project and a hands-on video course, check it out ๐Ÿ˜Š You get 25% off with the code ๐‚๐–๐๐Ÿ๐Ÿ“ ๐Ÿ’ธ Book: $59 Code & Book: $134 Video & Code & Book: $194 Bonus: If you buy it within the first week, you get the AWS Fundamentals book ๐Ÿ๐จ๐ซ ๐Ÿ๐ซ๐ž๐ž ๐Ÿ“• ๐Ÿ”— shop.awsfundamentals.com/buyโ€ฆ
24
17
94
14,524
Sandro Volpicella reposted
Milan Jovanoviฤ‡
 @mjovanovictech
Jul 5
Some of the best advice I got as a junior engineer: 1. Make it work 2. Make it pretty 3. Add safety with tests 4. Avoid over-engineering 5. Refactor only when needed Software engineering doesn't have to be complicated. All it takes is a simple process and lots of practice. What would you share with your junior self?
5
11
53
3,793
Sandro Volpicella reposted
Matt Pocock
 @mattpocockuk
Jul 5
The "should you read code" debate is dumb because the real decision isn't binary, it's a scale: 1. Reading every line of every diff 2. Scanning every diff, reviewing important lines 3. Ignoring diffs but understanding the 'why' of every PR 4. Spot checking PR's instead of reading every one 5. Ignoring PR's, but doing regular spot checks on the codebase 6. Ignoring the code, but spot checking agent traces to help improve the system 7. Ignoring both the code and the system, let models handle everything Where are you on the scale?
311
135
1,911
218,273
Everyone feels busy, nothing is produced
Tomasz ลakomy
 @tlakomy
Jul 5
Building with SCRUM:
0:11
3
436
Sandro Volpicella reposted
Tomasz ลakomy
 @tlakomy
Jul 5
Building with SCRUM:
0:11
18
51
791
125,869
Sandro Volpicella reposted
Tobias Schmidt @tpschmidt_
Jul 3
One company manages 6,000 AWS accounts with three people ๐Ÿ˜… Not 60. Not 600. Six thousand! ๐Ÿ”ฅ Each customer gets their own isolated account with the full microservice stack โ†’ 40 services, ~120,000 deployed instances, roughly 1 million Lambda functions across the fleet.
14
38
549
70,598
Sandro Volpicella reposted
Chris Frantz
 @frantzfries
Jul 2
Hiring for a product educator for @loops Remote, async, competitive pay, excellent health benefits No requirements around age/gender/location/experience To apply make a video about Loops
32
15
389
107,163
There are 1618 different SCPs in ControlTower. I would definitely go with the following: - AWS-GR_REGION_DENY: forbid all regions which you're not using - AWS-GR_RESTRICT_ROOT_USER_ACCESS_KEYS: forbid the creation of access keys for root users
2
1
4
493
- AWS-GR_S3_BUCKET_PUBLIC_WRITE_PROHIBITED: no public writes for s3 buckets - AWS-GR_S3_BUCKET_PUBLIC_READ_PROHIBITED: no public reads for s3 buckets
120
I deploy all my single-page applications via CloudFront and S3. But I stumbled upon one error repeatedly, and it is about routing and default behaviors. I think too few people understand why this is happening.
1
6
551
However, your API should return those error codes to your SPA. If a non-admin tries to access /admin, he should get a 403 error, and the SPA should render a "Blocked" page for him. This won't happen since CloudFront redirects again to index.html.
1
79
For that case, I typically use a CloudFront function that does one thing: - if URI = /api -> return origin response - if URI != /api -> return S3 origin index.html Fixed โœ…
1
71
After running AWS Fundamentals for over 3 years now, I'm happy to announce: WE HAVE A CICD NOW ๐Ÿ‘จ๐Ÿฝโ€๐Ÿ’ป So far, local deployments were more than enough.
1
2
576
But with more and more static pages, longer deployment times and builds, and the urge to ship feature after feature we finally have a simple CICD on GitHub Actions ๐Ÿ’ช๐Ÿฝ
2
69
I've read too often now Terraform instead of Transformโ€ฆ
268
AI is a multiplier, garbage in, garbage out. I love that. That means AI shouldn't stop you from learning things. You still need to understand the basics. AI just tells you "YES". You need to understand it. You need to judge it. You are responsible in the end.
2
1
373
You shouldn't be on the passenger seat and AI is driving. You should be driving and steer the AI what to do. Of course, it can figure out stuff for you. You can discuss database schemas, architectures, and design decisions.
1
103
But you should still feel the difference and decide what it should be in the end.
36
Load more