AWS CodeCommit event support landing in Sparta http://v.next. #serverless #go
Ref: https://docs.aws.amazon.com/codecommit/latest/userguide/how-to-notify-lambda.html
RT @abbyfuller: This is my first job working with other senior women and how could you ever go back? EVERYONE SHOULD HAVE THIS.
People wh…
‘The act of writing out “here’s who I am as a manager” is useful as a tool for introspection’ (via @Pocket) https://larahogan.me/blog/team-introspection/#tools-for-team-introspection
Bittersweet announcement: today marks my last day @ShiftLeftInc. I have very much enjoyed working here and know there are *huge* things yet to come.
Replying to @ShiftLeftInc and @ShiftLeftInc
’s technology is poised to transform how people conceptualize, inspect, and verify their code’s security posture. Thanks and best wishes to everyone there. 🙇♂️
Replying to @mweagle
As for me, I’m taking a short break in search of some sunshine. Will have more news to share in a bit.
Replying to @joshroppo
Appreciate that 🙇♂️. Us PNW’s need to work together to maximize collective lumen levels!
Replying to @kstewart
Thanks 👊 I need some of your Ironman power!
Replying to @realDavyHua and @ShiftLeftInc
Thank you - I’m glad I was able to help. Friendship will last beyond this day. You make us all look like slackers though. #armyOfDavy ✊
RT @sea_serverless: First Seattle Serverless Meetup of 2019 announced! #serverless
https://www.meetup.com/Serverless-Seattle/events/258603577
RT @wendynather: We don’t need more people who “help solve problems” by pointing them out. We need more people who actually solve those pro…
Limited time offer
Replying to @skpodila
ACT NOW! 😉
Has anyone become unaware of 4K TV frame interpolation artifacts? I can’t unsee them.
Replying to @perrito666 and @bketelsen
Prince 😢
RT @JackieTalkNerdy: Never forget that Prince performed the halftime show in the middle of a monsoon, with live instruments, live vocals, d…
Well, at least #SBLlll reminded me to rewatch this. 💜
https://youtu.be/6SFNW5F8K9Y
Sparta v1.9.1 - The CodeCommitment Edition 💕
Adds support for CodeCommit Lambda trigger events.
#serverless #go
https://github.com/mweagle/Sparta/blob/master/CHANGES.md#v191---the-codecommitment-edition-
Replying to @mweagle
Doc fixes thx to https://github.com/Daniel-Cavallaro and some internal cleaning up.
Removed, the Yoda conditionals are: https://staticcheck.io/
https://goreportcard.com/report/github.com/mweagle/Sparta
Replying to @oter
Thanks! I’ll still be around & look forward to catching up. 🙇♂️
Replying to @catlgrep
Thanks! Looking forward to next part of the journey. 🙇♂️
“Properly integrated data science, however, is a game changer you cannot afford to ignore. Embrace data science with a DevOps mindset.” (via @Pocket) #longreads https://www.datascience.com/blog/why-is-it-so-hard-to-put-data-science-in-production
ICYMI... https://twitter.com/mweagle/status/1092298863954714624
MFW the snowpocalypse is causing intermittent power outages.
Replying to @mweagle
Intermittent ➡️ Permanent
Replying to @mweagle
PowerOps FTW 🙌
RT @spartaserverle1: Welcome to the new home of https://gosparta.io announcements.
https://twitter.com/mweagle/status/1092298863954714624?s=20
Replying to @garnaat and @benkershner
Possibly only ever used once: https://www.seattletimes.com/seattle-news/politics/mayor-nickels-didnt-ask-to-have-his-street-plowed-report-states/
The mystery deepens...
Replying to @benkershner, @tmclaughbos and @garnaat
I’ve lived in near Boston, South Bend, and Chicago.
I suppose technically today’s weather does count as snowfall.
RT @spartago2: Naming is hard.
It’s interesting to hear some people tell their story, especially when you were a first hand witness.
Replying to @southpolesteve
Ugh. 🙏
“Development teams and their product managers solve adjacent, but different problems.” (via @Pocket) https://www.mironov.com/infra/
“The meetings should have a regular cadence, scheduled either once a week or biweekly and only cancelled for pressing circumstances — and if they have to be cancelled, it’s a good practice to let the other person know why...” The Importance of One-on-Ones https://css-tricks.com/the-importance-of-one-on-ones/
“This shone a light onto a bigger issue: it made us realize that our attempt to align all our hiring processes had led us to focusing on, and optimizing for, the wrong skill set.” (via @Pocket) https://circleci.com/blog/what-we-ve-learned-about-hiring-engineering-managers/
“It intentionally moves the complexity of thinking about team size up the chain and requires the company to get better at planning and communicating goals, and being disciplined about prioritization.” https://kellanem.com/notes/on-team-size
Sac-town is fun to watch and @swipathefox is going to be a star.
RT @abbyfuller: like maybe instead of instantly denying whatever we say, try listening?
Replying to @dubrie and @muratdemirbas
Possibly also eternal.
https://www.thestranger.com/slog/2016/12/08/24738000/and-now-for-the-annual-seattleites-cant-drive-in-snow-film-festival
Replying to @conikeec, @VladAIonescu, @realDavyHua and @spartago2
Voldemort-full?
Hi @QuinnyPig - this is a great interview and heads up that at least in Overcast the episode image is empty.
https://www.screaminginthecloud.com/ is 💯
RT @sea_serverless: The inaugural Seattle Serverless 2019 Meetup is finalized!
https://www.meetup.com/Serverless-Seattle/events/258603577/
Replying to @QuinnyPig
Most definitely. Although I think my unwavering agreement with your take might make for a short conversation.
Also, https://twitter.com/kstewart/status/945831658590105600
Replying to @QuinnyPig
Anyone at #awswishlist looking to bump a feature?
https://twitter.com/mweagle/status/896057169979756544?s=20
Replying to @robotterror
Supremely Respectful Empath?
🤔
Replying to @AWSbrett and @QuinnyPig
Maybe? Possibly as a layer that taps/transforms API responses based on SSM config?
However delivered, something like this capability would be 👌
Replying to @realDavyHua
A to the K
RT @lindydonna: What reading material would you recommend to someone who is trying to improve diversity and inclusion in an organization? T…
Replying to @edyesed
Deep Cloud Nine
Replying to @lindydonna
TIL as well. Thx for posting.
“We look for companies based around projects that can make a single developer look like a “hero” by making her/him successful at some important task.” (via @Pocket) #longreads https://www.madrona.com/the-remaking-of-enterprise-infrastructure-investment-themes-for-next-generation-cloud/
🙄 https://twitter.com/JoeConchaTV/status/1093236280815771648
Replying to @mweagle
2/ I have some #serverless localhost v. cloud Dev n’ Testing thoughts. As a teaser: https://twitter.com/mweagle/status/972197580212912128
1/ Twead incoming...
Replying to @mweagle
7/ 3. Testing in the cloud forces observability. If you can’t understand why a test fails, you need to increase system transparency. That transparency is *also* useful when the system fails in production. Because it will fail. Users don’t care about passing tests.
Replying to @mweagle
6/ 2. Cloud-native development opens up the ability to test with team-wide shared state. How many times has a localhost-passing feature failed in stg/prod because of DB state? Tests against empty state ignore system state/data evolution. Shout out to the DBRE crew.
Replying to @mweagle
5/ 1.1 Unplanned work: becoming less manageable since at least 2006: https://www.computerworld.com/article/2563263/it-management/unplanned-work-is-silently-killing-it-departments.html
Replying to @mweagle
4/ 1. Developing and testing in the cloud pushes integration costs left in the value chain. Integration costs are the exponentially increasing unplanned work that shows up as “deployment pain”. Code a customer can’t access is as valuable as code never written.
Replying to @mweagle
3/ Disclaimer: not everyone, not all the time, not always possible, hyperbolic by intent. But I think it should be the default position.
Replying to @mweagle
11/ 6. Integrating cloud dev into a standard workflow increases overall cloud familiarity. This creates conditions for a serendipitous #servicefull approach: rather than coding it, is there a service *you can access* that handles the 80%+ case?
Replying to @mweagle
10/ 5. It mitigates the frustrating feeling of “feature done, just need a deploy” that disincentives sufficient operational awareness. If you’ve already “done the deploy” as part of normal development, that last hurdle can feel less imposing/aggravating.
Replying to @mweagle
9/ 4.1 What else does someone need to know? Can they know it? How can it be exposed?
Replying to @mweagle
8/ 4. The observability imperative can open up a dialog about operator empathy. You (well, the 3am version of you or your team member) will really appreciate the ability to more deeply inspect the internal system state using a phone and an updated config param.
Replying to @mweagle
16/ 8. Ultimately developing & testing against the cloud shares similarities with meta-engineering practices: https://blog.acolyer.org/2018/01/17/some-thoughts-on-security-after-ten-years-of-qmail-1-0/
Replying to @mweagle
15/ Code them up when you’re out of the flying metal tube.
Replying to @mweagle
14/ 7. Yes, there are places where connectivity isn’t available. That’s ok. Consider that the customer-facing service is still running, so there are on-call operators who need higher levels of access. Instead, sketch out some crazy ideas in a notebook.
Replying to @mweagle
13/ 6.2 If a normal dev workflow is about configuring infrastructure and verifying expectations, it’s a much shorter jump to composing systems from those higher level services.
Replying to @mweagle
12/ 6.1. Those cloud services often require “infrastructure configuration”, but if that’s done by someone else, you may not even consider it a viable option since it’s coordination. And coordination, well, you know, that sounds like a meeting....Yeah, no.
Replying to @mweagle
19/ PS: I also have some milquetoast thoughts on `latest`: https://twitter.com/mweagle/status/992516555811405824
Replying to @mweagle
18/ 9. I understand the need for quick feedback. However, if a deploy is ~60s (CloudFront 👀) I’ve made a choice to accept that so that I don’t need to deal with 60 hour meetings trying to get a feature to all the way to production.
Replying to @mweagle
17/ 8.1 What behavioral practices does CloudFirst development and testing incentive? Does testing in the cloud eliminate potential sources of system (both technical and organizational) flow interruptions?
Replying to @ben11kehoe
Yep. Development feedback cycle times *are* important, but that’s one variable in a messy optimization problem.
Replying to @jeffhollan, @PaulDJohnston, @ben11kehoe and @Serverlessconf
Yep.
Replying to @jeffhollan, @PaulDJohnston, @ben11kehoe and @Serverlessconf
To be a bit more forthcoming: I have no problems with editing locally. What I advocate against is executing locally.
Replying to @jeffhollan, @PaulDJohnston, @ben11kehoe and @Serverlessconf
It’s going to be bumpy 😉
Replying to @abnerg and @stackeryio
RT @lindydonna: Really great points about “local development” when building modern cloud apps.
To add on to Matt’s thoughts: hybrid optio…
Replying to @edyesed, @PaulDJohnston, @ben11kehoe, @jeffhollan and @Serverlessconf
Yep. I would like “Cloud Native Chaos Monkey” support in all cloud services s.t. I could inject faults across the higher level services that are composed for a deliverable. How can I deliberately force DDB IO exceptions as part of a test run?
Replying to @richburroughs
Same. I have worked on projects that inline manage schema migrations, but keeping the seed data synchronized across local dev is its own version skew madness :)
Replying to @FarrahC32
😂 - I remain a happy Wells Fargo abstainer.
Replying to @turgon
🙇♂️ - We will get there together. ☁️🥇
RT @richburroughs: Lots of #hugops to anyone working on this though. I’ve been through two outages where we lost entire data centers in my…
Replying to @kstewart
🙇♂️. I fondly remember our coffee walks 😄
Replying to @kevinswiber and @kstewart
Same (more than once). 😄
Replying to @jessehattabaugh, @lindydonna and @DavidWells
It never is. If your current approach works for your team and organization then no worries & keep rolling.
For certain types of problems (eg: Step functions triggered by DynamoDB Streams), there isn’t really a localhost equivalent.
I am a dogmatic pragmatist.
Replying to @mpchlets
I think that there’s a PhD thesis in waiting for SemioticOps.
Replying to @brasten
Agree & I also would like better CloudFirst DX.
https://twitter.com/mweagle/status/1093599683551801344?s=21
RT @adrianco: @JoeEmison @ben11kehoe @mweagle @edyesed @PaulDJohnston @jeffhollan @Serverlessconf @GremlinInc @thundraio I’m working on a m…
Replying to @wclarknewton
Sure! Agree both might be better where possible with suggestion that the default mindset be “always must run in cloud, some subset might run local” rather than “always must run local, some parts might run in cloud”.
RT @ben11kehoe: @mweagle instant dev gratification should not trump pipeline TCO
Even more importantly, is that a @github whiskey glass and how does one obtain one? https://twitter.com/angryseattle/status/1093763382333792259
👋 to the new Twitter friends. I don’t have a SoundCloud, but recommend this as a good Twitter profile background:
https://twitter.com/aprilwensel/status/1059304143678894080?lang=en
Replying to @dtauvdiodr
💯 agree & I could have worded this better. This shift needs *more* teamwork and fewer silos.
RT @tinyrobots: I will be speaking at @sea_serverless on February 21st in #seattle
“Safe Lambda Deployments”
#awslambda #serverless http…
RT @turgon: @mweagle @wclarknewton My advice as someone who’s practiced doing both is the fast feedback from local dev gets offset by the t…
RT @ben11kehoe: @jlhcoder @prestomation @forrestbrazeal I think we need to distinguish between local execution of user code & local emulati…
Replying to @editingemily
KARL!
That is tremendous. 😂
Possibly fictional slice? I’m still looking for real pizza in Seattle. 😉 https://twitter.com/HistoryLink/status/1094331972179107841
RT @kstewart: Me too. Going on 15 years now. https://twitter.com/mweagle/status/1094333015671504896
Wow. https://twitter.com/espn/status/1094399890820644864
Replying to @alicegoldfuss and @nicolefv
This place does a much better job:
http://whitneyplantation.com/
Well, this should be a good read wherever you stand on the #serverless movement:
Cloud Programming Simplified: A Berkeley View on Serverless Computing
https://www2.eecs.berkeley.edu/Pubs/TechRpts/2019/EECS-2019-3.pdf
Current status: Certificate must be in ‘us-east-1’.
😢
TFW you’re waiting for CloudFormation to provision a fresh API Gateway with a custom domain.
“For regional APIs, you need to use an ACM certificate from the same region as the API.” 🤦♀️
Current status: going for a walk.
Replying to @DeleuGyN
Nothing, but ran into that after:
https://twitter.com/mweagle/status/1094700689748414466?s=21
Replying to @ewindisch
😂 That sounds like a great idea. I’m even willing to push it to Tuesday 😀
“Serverless computing will become the default computing paradigm of the Cloud Era, largely replacing serverful computing and thereby bringing closure to the Client-Server Era.”
🎤 ⬇️ https://twitter.com/mweagle/status/1094692364373782528
What else could we add to this solution? https://t.co/tHIiAL4AmX
Replying to @robotterror
🤔 I’m not so sure. Anything unkind or thoughtless would be a giveaway 😀
My buddy Marc has released a training program that walks you through some real-world SaaS apps. 🍾🎉 https://twitter.com/saasbooster/status/1093610801829679104
Replying to @mweagle
Marc’s why story: https://www.youtube.com/watch?v=uUTVHaMwyek
Today is Day 1 for me @Lyft! 😊
I’ll be leading a Seattle-based ML team to help create even better transportation experiences. Stay tuned for even more #serverless with increasing amounts of ML mixed in!
RT @forrestbrazeal: “Serverless computing will become the default computing paradigm of the Cloud Era.” Here is a rare academic paper that…
Had a great onboarding Day 1 @lyft and thanks very much to everyone for the kind words! 🙇♂️
Ever thought about having your own Day 1 with us? We’re hiring in SEA!
https://www.lyft.com/careers?department=engineering&location=seattle%252C%2520wa https://twitter.com/mweagle/status/1094997269529542661
RT @ShiftLeftInc: ShiftLeft Raises $20M Series B financing, let by @thomvest, with participation from @SineWaveVC, @BainCapVC and @Mayfield…
Replying to @danselstory and @lyft
Too early to tell & we will look at all options depending on the issue.
Replying to @benkershner
Appreciate you saying that. 🤗
RT @benkershner: Just so we’re all very clear: you *WANT* to work for/with Matt. He’s smart, well-opinionated, and very much just a good pe…
Replying to @benkershner
Day 2 status update
RT @foobar_codes: ⭐️New interview is out! ⭐️⠀ This week I interview @ben11kehoe #AWS #Serverless Hero and the has been doing lots of server…
Day 3 status update
Replying to @realDavyHua
Objects in GIF are closer than they appear. 😉
Replying to @lindydonna, @lizthegrey, @mipsytipsy and @o11ycast
Yes! Looking forward to listening.
Relentless IT 👍 https://twitter.com/wojespn/status/1095751682569523200
Whither Picoservices? https://overcast.fm/+FyQ_33rMc
Day 4 mood
Replying to @joshroppo
True! Time for s’mores.
Unexpected @lyft behavior: lingering in bathroom to determine if soundtrack is from Aretha or 3rd Bass. Both are possible.
It was Aretha.
RT @dbsmasher: Ops people.....we still got a lot of work to do....
Inbox Nero: let your unread count grow without bounds
RT @lindydonna: To prove a point:
Please RT if you don’t have a CS degree and you have a job in tech. https://twitter.com/lindydonna/status/1095878354023129088
Nearly done wrapping up the in-progress API-GW custom domain support. #serverless
Replying to @edyesed
Fantastic.
Replying to @brianleroux and @lindydonna
There’s still time. 😉
Day 5 onboarding update
Replying to @chuckm
If I think I’m still onboarding on day 500 please send help.
srsly though, @lyft onboarding was a week of awesomeness.
RT @IOpipes: Don’t miss the chance to dive deep into building data pipelines & scalable enterprise #Lambda deployments at this month’s @sea…
Good conversation https://overcast.fm/+E_eMHsMs8
Replying to @EricaJoy
Makes me an even bigger fan of @swipathefox
RT @spartago2: Sparta v1.9.2: The Names Edition 📛
Associate a custom domain name & ACM cert with your API Gateway instance. #serverless
R…
Replying to @skpodila and @lyft
Thank you!
Replying to @grepory
Same. Currently on Ep 10. Fantastic.
“Deployless development will look a lot like distributed smalltalk.” (via @Pocket) https://medium.com/@doctor_julz/what-comes-after-serverless-840032dd4ba8
‘You can address issues that are damaging to productivity, operability and morale, but only way to “fix technical debt” is “rm -rf”.’ (via @Pocket) #longreads https://kellanem.com/notes/towards-an-understanding-of-technical-debt
RT @sea_serverless: Come join us this Thursday and help kick off the Seattle Serverless Meetup series for 2️⃣0️⃣1️⃣9️⃣!
https://t.co/2R6B…
Wondering if WIP slack is similar to liquidity...🤔
“How do you fund it?” https://overcast.fm/+BYGCcRUQ
👍*💯 https://overcast.fm/+G0X_FAeBA
Replying to @ingvar_ua and @AWSSecurityInfo
Fabulous! 🙌
Quick break from Day 1 at SEA @lyft for this important announcement. #theR
Day 1 @lyft at SEA status
Look forward to seeing the Seattle #serverless members at this Thursday’s Meetup!
https://www.meetup.com/Serverless-Seattle/events/258603577/
RT @mweagle: Look forward to seeing the Seattle #serverless members at this Thursday’s Meetup!
https://www.meetup.com/Serverless-Seattle/events/258603577/
“[S]erverless architectures could help build AI pipelines that take automation to a new level.” (via @Pocket) #longreads https://thenewstack.io/how-serverless-platforms-could-power-an-event-driven-ai-pipeline/
RT @adjohn: Hope to see some of you tonight at the Seattle #Serverless meetup! https://www.meetup.com/Serverless-Seattle/events/258603577/
RT @kstewart: I am so lucky to work with @randommood who leads our Data Engineering team @fastly. She is looking for TWO engineering manage…
RT @carmatrocity: A lot of DMing/asking me if @travisci is closing. I don’t know? I do know it’s not going to be the same Travis going forw…
Replying to @sallamar and @forrestbrazeal
Thx @sallamar !
Honored to be joining a great group.
Replying to @chrismunns, @IamStan and @jeremy_daly
Thanks! Honored to be a member. 🙇♂️
Replying to @benkershner, @chrismunns, @IamStan and @jeremy_daly
Thanks!
Replying to @QuetzalliAle and @rossbarich
Thank you! 🙇🤙
Replying to @kstewart
Most appreciated. Thank you. 🤗
Replying to @IamStan and @kstewart
Please don’t judge me 😉
Replying to @kstewart and @IamStan
Hard agreement. Congrats.
Replying to @mavi888uy, @jeremy_daly, @IamStan, @aileengemma and @OyeHooye
Thank you @mavi888uy! 🙏
Replying to @realDavyHua
Thanks @realDavyHua! 👊
Replying to @ben11kehoe, @jeremy_daly, @IamStan, @aileengemma and @OyeHooye
Thanks @ben11kehoe! 🙏
Replying to @suryaj, @jeremy_daly and @IamStan
Thanks @suryaj & great catching up with you last night! 🙏
Replying to @rossbarich
Thanks @rossbarich!
Replying to @perrito666 and @realDavyHua
Same to you friend 👊
Replying to @alexbdebrie, @jeremy_daly and @IamStan
Thanks @alexbdebrie! 🙏
Bad mentorship ➡️ Bad internship experience
Mentor is a verb. https://overcast.fm/+MdF5UUSQ0
RT @QuetzalliAle: @mweagle A lot of people think they’re good mentors by defacto, if they know a lot of a subject. But being a mentor means…
Replying to @QuetzalliAle
Agree & I think it’s possible to get better at it, but it’s a deliberate practice.
Replying to @jbesw, @esh and @jeremy_daly
Thanks @jbesw!
It can’t possibly be the USB-C to HDMI dongle that’s causing my MBPs Networking and Bluetooth stacks to degrade and then fail.
Narrator: He would soon learn how wrong he was.
srsly? The TouchBar ESC key is frozen. I miss the 2015 MBP edition.
Replying to @abbyfuller
wat.
I would like to file a grievance with the proper authorities. #formANDfunctionPlz
Replying to @halifaxbeard
Will do - thx.
Replying to @chrismunns
Wait, it’s over already?
I need to read these.
Replying to @edyesed
The R in IOT stands for Reliability.
Replying to @IamStan
I’m...still somewhat dumbfounded that this can happen.
Replying to @kstewart and @IamStan
No so much ❤️ here for the new MBP. That lab needs less funding.
AppleTV remote 👀
“We have observed that both researchers and engineers may treat configuration (and extension of configuration) as an afterthought.”
https://papers.nips.cc/paper/5656-hidden-technical-debt-in-machine-learning-systems.pdf
Replying to @robotterror, @edyesed and @Twitter
Great first week @lyft SEA.
Replying to @windlessuser and @golang
Yeah, it can be a bit of a pain. Not sure if node or go makes it any better 😀
Replying to @windlessuser and @golang
Excellent!
I’m thinking that my JIRApertise is something that will need to improve.
Replying to @abbyfuller
There are so many things about SEA I will never understand.
http://www.mattshotdogs.com/menu.html
Replying to @tmclaughbos, @JasonCutrer and @abbyfuller
Replying to @listonb and @abbyfuller
I am lost for words. Sending you some pepto.
http://www.jpaulmorrison.com/fbp/noflo.html
I find the notion that serverless/k8s/anything heralds the arrival of “NoOps” to be very misleading.
Replying to @mweagle
Since there is frequently 🐶-piling on the “serverless” term as misleading, or even potentially oxymoronic, the idea that “NoOps” could ever be a thing seems a bit odd.
Replying to @mweagle
I’m all for NewOps, DiffOps, LessOps, SharedOps, SysOps, whatever works for you, but the “NoOps are coming” headline is something the millennial army needs to help retire.
Replying to @chrismunns
It’s from https://searchcloudapplications.techtarget.com/definition/noops , linked from https://www.zdnet.com/article/theres-no-ops-like-noops-the-next-evolution-of-devops/
Replying to @chrismunns
Pitch: We’ve developed NoPlatform to enable NoOps.
This is a good story. 🐬🙌
https://blog.therainforestsite.greatergood.com/diver-dolphin/
Replying to @kstewart
Any special sendoff meal planned?
Replying to @kstewart
That is a solid plan 👊
#peanutPunchFTW
Replying to @perrito666
Oh, nice!
“If you want the wrong answer quickly, feel free to checkpoint without idempotency. But if you want software that works, your tasks need to be idempotent.” Checkpointing Failure (via @Pocket) https://blog.0x74696d.com/posts/checkpointing-failure/
“What lessons can we bring in from the database world?” https://www.slideshare.net/AliceZheng3/the-challenges-of-bringing-machine-learning-to-the-masses
The 70/20/10 testing distribution has a lot of merit. It also seems fitting that the mobile layout makes it nearly impossible to read.
https://testing.googleblog.com/2015/04/just-say-no-to-more-end-to-end-tests.html
I’m honored to be a new AWS Serverless Hero, continuing to support and expand the #serverless community.
Do you have questions about something serverless? We’re all here to help 👋
https://aws.amazon.com/developer/community/heroes/#Serverless_Heroes
Design patterns for high-volume, time-series data in Amazon DynamoDB (via @Pocket) #longreads https://aws.amazon.com/blogs/database/design-patterns-for-high-volume-time-series-data-in-amazon-dynamodb/
RT @rakyll: One tip: If something is not working for you, document why it doesn’t. But avoid claiming that it ain’t going to work for anyon…
Replying to @geoff_baskwill and @alexbdebrie
😂 - I’m new to these parts.
Looking forward to continuing to move things forward, but full credit goes to the talented and focused @lyft ers that made today possible.
Replying to @geoff_baskwill and @alexbdebrie
Just barely 😉
RT @abnerg: Cloud-side development: Wherein we channel @ben11kehoe @QuinnyPig @mweagle @prestomation @jlhcoder and others to announce @stac…
So we meet again JIRA...
Replying to @robmccauley
Thanks @robmccauley 🙇♂️
“Happy services are all alike; every unhappy service is unhappy in its own way.”
- Anna Micronenia
“This makes Argo workflows highly scalable, reliable, easy to extend, and portable between Kubernetes clusters.” (via @Pocket) https://blog.argoproj.io/introducing-argo-support-for-google-container-engine-gke-minikube-and-docker-304f1af8aabb
Great post @sallamar 👍
Incidents — Trends from the Trenches (via @Pocket) #longreads https://m.subbu.org/incidents-trends-from-the-trenches-e2f8497d52ed
Please unroll @threadreaderapp https://twitter.com/esh/status/1100703375409082369
Replying to @richburroughs, @sallamar, @vinaybannai and @drensin
Config-based outages also cited as motivation for https://research.fb.com/wp-content/uploads/2016/11/holistic-configuration-management-at-facebook.pdf
Replying to @sallamar, @richburroughs, @vinaybannai and @drensin
Yep - your categorizations are 👌
RT @sallamar: @mweagle @richburroughs @vinaybannai @drensin Broadly it includes
- Automated CI/CD releases - Semi-automated deployments l…
Great post. Recommended. https://twitter.com/sallamar/status/1100463022865149952
RT @juliaferraioli: We already know that measuring value with LoC (lines of code) is a terrible idea. Using number of commits instead is no…
💯
Commits are incidental. Prefer measuring impact rather than inputs. https://twitter.com/rakyll/status/1100494633241436160
Is there a sane JIRA Kanban workflow?
Asking for a friend.
Replying to @robottaylor
I used the term “actively work hostile” earlier today and I feel that’s not terribly inappropriate.
Thinking that a whiteboard and some Post-It notes is is likely to spark more joy than JIRA.
Replying to @tmaiaroto
Wanted: meta-study on project estimate accuracy as a function of input fields.
Replying to @metz123
I like it.
Replying to @systemalias
Channeling Embid...
Replying to @ben11kehoe
Problem solved: https://www.doublerobotics.com/
RT @kstewart: No. https://twitter.com/mweagle/status/1100884013160423424
Replying to @kstewart
JQL is not my sprit language.
Replying to @QuetzalliAle
I will say it’s powerful. But I’m not sure that power is always needed.
ServerlessDays BOS will be wicked awesome. https://twitter.com/ServerlessBOS/status/1098965859274579968
Replying to @QuinnyPig and @adrianco
AWS PageMaker?
There’s a lot of 😎 stuff we’re working on and JIRA is going to have get on board that train.
Please unroll @threadreaderapp https://twitter.com/abbyfuller/status/1100964237118078977
Replying to @suryaj, @CAinc and @trello
Please no.
JQL and I will come to an understanding :)
@windlessuser pushing #serverless forward! 👊 https://twitter.com/saasbooster/status/1100250430704156672
Replying to @PaulDJohnston
I’ll stand with you on on that 🤝. My default priors: * Small functions * For a single logical domain * Transactionally deployed as a set (per func scaling, POLA, metrics, FinDev) * Asynchronously cooperating where necessary via events
JQL and I have come to an uneasy truce on how to make a Kanban board for JIRA, and it’s now (sort of) working.
Reserving the right to delete this Tweet in 48 hours.
Ex. A for the Defense in the “People vs Automation is Free” trial.
Excellent. https://overcast.fm/+FyQ8dXfk0
Replying to @kstewart
😂
Is http://no.dev taken yet?
Replying to @edyesed
http://meghantrainor.tech 🤷♀️
Replying to @chuckm and @luiscolon1
How to Build a Better Machine Learning Pipeline https://pocket.co/xIEt6S
The Key to Building Data Pipelines for Machine Learning: Support for Multiple Engines https://pocket.co/xIEtfG