Luis Morales @_moralesl

Solutions Architect @AWSCloud ☁️ Underscore as in JS naming conventions ⇒ Opinions are my own München, Bayern Joined January 2017

Tweets

33
Followers

58
Following

351
Likes

80

Stefan Smith @[email protected] @smith_stefan

3 years ago

I've often said that with #serverless: (1) the infra primitives map much more closely to your application's control/data flow, (2) AWS is your application runtime and (3) infra configuration is your (higher-order) application programming language.

1 2 5 0 0

Gregor @ghohpe

3 years ago

Getting ready for an awesome #serverless office hour with @_moralesl and @julian_wood Starts in 25 mins!

Gregor @ghohpe

3 years ago

Getting ready for an awesome #serverless office hour with @_moralesl and @julian_wood Starts in 25 mins! https://t.co/0YTAtYuEoN

1 6 45 0 9

1 4 16 0 1

Download Image

Gregor @ghohpe

3 years ago

Infrastructure as Data Structure (often euphemistically called Code) is so 2016. Hear what happens when you combine Infra as actual Code (#iaac), design patterns, and serverless! Live #serverless office hour session Tuesday at 10 PDT | 18 UK | 19 CEST youtube.com/watch?v=wOnDGo…

1 6 45 0 9

Eric Johnson @edjgeek

3 years ago

When developing #Serverless applications it’s best to debug in the cloud as much as possible. This is why we created SAM Accelerate. I am excited to say that as of today, Accelerate is generally available (ga). github.com/aws/aws-sam-cl…

3 24 89 0 6

Ryan Breslow @ryanbreslow

4 years ago

It’s official: Bolt is now the first tech unicorn to permanently switch to a 4 day work week 🚀⚡️🔥 Our 3 month experiment proved every core thesis: Heightened 1/ Productivity 2/ Engagement 3/ Wellness We’re never going back and here’s why 👇

210 2K 11K 0 1K

Uwe Friedrichsen @ufried

4 years ago

new post about the disruption delay observation i made: it takes about 20 years until disruptive changes in IT reach mainstream ("disruptive" regarding how we *do* or *use* IT). helped me to understand a lot of contradictions better: ufried.com/blog/disruptio…. enjoy if you like ;)

3 8 15 0 0

Alex Casalboni @alex_casalboni

4 years ago

⚡ New feature ⚡ AWS Lambda Power Tuning now allows you to compare 2 tuning results on the same chart 📈 For example, here I'm comparing 2 Python implementations that compute prime numbers up to 1M (with and w/o numpy) 🐍 and numpy wins! 13% faster & cheaper at 1.8GB 🚀

2 44 107 0 8

Download Image

Nick Coult @nickcoult

5 years ago

With a bit of work, it’s possible to have the same container image in ECR be used for running a load balanced web service in AWS Fargate, or a web service with API gateway in AWS Lambda. 1/x

2 22 96 0 11

Satinder Kaur @SatinderKTester

5 years ago

Amazing 99 minute workshop on “Testing in production and why would we ever do that” by @a_bangser @ministryoftest Made a quick sketchnote on the workshop.

1 12 22 0 5

Download Image

Pahud Hsieh @pahudnet

5 years ago

Running K3s cluster with the latest T4g instances with cdk-k3s-cluster is just one single #awscdk statement :-) copy @mreferre

2 6 17 0 1

Download Image

Cory House @housecor

5 years ago

A poorly-designed solution may seem impressive. Why? Because it’s complex and unapproachable. So it looks like it was hard to build. A well-designed solution may seem unimpressive. Why? Because it’s simple, and approachable. So it looks like it was easy to build.

8 84 372 0 9

Cory House @housecor

5 years ago

Some teams claim they're "too busy" to: 1. Write tests 2. Speed up the build process 3. Configure CI / CD 4. Mock the API 5. Configure linting / autoformatting 6. Do code reviews Yes, these things take time. But, in the long-run, these things *save* time. ⏳

48 413 2K 0 105

Massimo Re Ferrè @mreferre

8 years ago

A gentle reminder that the only way to avoid lock-in is to lay down on the sofa and do nothing. You're welcome.

6 20 104 0 0

Marko Denic @denicmarko

5 years ago

Mystery Solved!

206 10K 37K 0 452

Download Image

Andy @_andys8

6 years ago

"you would be surprised at how many times having too much code is the first symptom of a poorly understood problem" Source: @atopbook

0 7 20 0 0

Ives van Hoorne @CompuIves

6 years ago

I've seen far more projects fail from overengineering rather than from underengineering. It's very easy to overengineer and I need to constantly remind myself to keep it simple.