Discover and read the best of Twitter Threads about #VelocityConf

Most recents (24)

Ugh, speaker feedback for #VelocityConf is... useless because of low feedback counts, usually the most disgruntled people.

There are... a total of ~5 reviews across my workshop & talk, who hated them. I've spoken to or seen tweets from >>5 people who really enjoyed the talk.
QCon's universal feedback system is far more useful, because everyone at least thumbs up or downs every talk... and then has the option to add more written feedback later.

I'm disinclined to believe anonymous feedback that's harshly negative and 180 degrees from what I hear f2f.
and especially when it's from less than 10% of my audience. If someone thinks my content is "banal" or "just advertising Honeycomb" and so far beneath them, then maybe they shouldn't have come, because what I'd cover was _very_ clearly advertised on the tin in the abstract...
Read 4 tweets
.@jmickey_ is delivering a case study about @CondeNast developing a k8s/AWS platform for providing a platform for software developers. #velocityconf
@jmickey_ @CondeNast "Service meshes are cool, but not everyone is ready for them. People are just getting started with k8s." --@jmickey_

and the choices from the CNCF landscape map are overwhelming. #velocityconf
So many domains to worry about when productionizing k8s - app delivery, logging, monitoring, ingress, auth, supporting infra... #velocityconf
Read 18 tweets
I'm hosting @AloisReitbauer in the Overcoming Obstacles track at #velocityconf! He's telling us about avoiding technical debt in our deploy pipelines.
@AloisReitbauer Dynatrace moved away from a gatekeeper traditional NOC and ops model in 2014 and moved towards SRE and NoOps/production ownership.

1500 on-prem managed services now, and 35 clusters with 7000 shared tenants today. #velocityconf
Quality and speed down't have to be in conflict; they are moving faster and have higher quality.

How? Production ownership. Continuous feedback on requirements, short feedback loops (<1h), decoupling of deployment & release #velocityconf
Read 19 tweets
Lessons at #velocityconf from @davecheney on culture & community that I also intend to briefly touch upon in my #KubeCon keynote, because a white supremacist/misogynist attendee has not (yet) been banned... Harassment and discrimination are simply unacceptable. codes of conduct are very important words on paper.if you define merit in your projects in terms of who has got the most code, you are excluding other forms of contribution
@davecheney Update: the white supremacist has in fact been banned from KubeCon.
late-breaking news from last night that I missed, apparently.
Read 3 tweets
At #velocityconf, @desplesda and @parisba are explaining how the videogame industry is a sophisticated producer and consumer of telemetry.
@desplesda @parisba It used to be that you shipped boxed software, but today our games are interconnected and massively online. Tens of millions of people using Steam at any moment. #velocityconf
Their key telemetry: installations/uninstallations (for acquisition/churn), launches/exits (stickiness), interactions/purchases (for ARPU, stickiness).

It's serious business. #velocityconf
Read 24 tweets
I'm excited to see @wiredferret's take on build vs. buy. she says that open source software is like free puppies you find in a box...

they aren't actually free in the long term. #velocityconf
@wiredferret purchase cost is not the expensive part of owning a dog, it's the ongoing maintenance - shots, food, leashes, walking, vet trips, puppy class...

plus unknown costs - shoe replacement, wall repair, remedial training, emergency vet trips, rent increases... #velocityconf
You can't anticipate everything that's going to happen in parenting, puppies, and software.

What does "Free software" mean? is it as in price, speech, beer, or... puppies?

as @jwz says, linux is only free if your time is worthless. #velocityconf
Read 20 tweets
Every airplane has an error budget... and you are not going to fly today on that plane, if it is not within normal maintenance bounds, says @wiredferret #velocityconf
@wiredferret 100% reliability means infinitely fragile. We need to have the _right_ amount of slack in our systems. Operational != perfect. #velocityconf
We have layers of abstraction to help us be more productive, but it took hard work to make things _seem_ easy. the work is just moved around, rather than removed.

Toil that's been automated still is work... just performed by a computer (but if that breaks...) #velocityconf
Read 11 tweets
Next up is @0xa6ea on implementing security by design! #velocityconf
@0xa6ea 100% is never the right target for reliability, as we know as SREs, because our customers do not actually need 100%.

Match the design of your product to the risk profile of your customers. #velocityconf
Both security and reliability are critical use cases. And sometimes they come together, such as in the case of the secure password storage service that required a HSM card to start (which was in a safe, whose code was in the password manager that was down)... #velocityconf
Read 10 tweets
Next up at #velocityconf is the inestimable @cyen, on the value of observability to developers and operators!
@cyen We have to be able to see production through our customers' eyes, and bridge the gap between developers and operators. #velocityconf
But it's not just devs and ops, it's so many other job roles each of which have different success metrics - support, sales, finance, product/marketing...

but all of us ultimately care about customers and wanting to know how they're doing. #velocityconf
Read 15 tweets
Prof. James Mickens is giving a hilarious talk about the ills of modern technological society, including how Twitter is awful... #velocityconf
after having needed to tell children about Nazis, anti-Semitism, and the triple parentheses: "Let's just leave this place, everything is death, stop touching the canisters. Don't start a Twitter account, it's like starting smoking today in 2019" --Prof. Mickens #velocityconf
[ed: and there's a certain irony that I'm livetweeting this.]

It's not just Twitter that has a content moderation problem, it's Facebook too, and every other platform that doesn't want to take accountability for what's happening on this platform. #velocityconf
Read 8 tweets
as usual, liz's recap is a clear and crispy version of my talk, and you should read it if you're intrigued by the idea of testing in production.

(but I've still got the edge on rainbows muahaha 🌈🌷💜💙💚💛🧡❤️🌸🌟🌈)
favorite moment of this afternoon was afterwards, when a few -- multiple! -- people with formal security and QA backgrounds came up and told me even MORE reasons to urge testing in prod. 🤗🥰
second favorite moment has to be at the end when I was marveling over my own moderation and self-restraint, and @lizthegrey piped up "I'm a good influence!" sotto voce, front and center. 🤣🥳
Read 4 tweets
I'll be livetweeting @mipsytipsy's talk on testing in production in a few minutes... #VelocityConf
@mipsytipsy The room is full, and we found her! [ed: hi, I was marshalling her from her hotel! this place is a twisty maze!]

People feel trepidation or like they're yoloing like a cowboy when they hear "testing in production". It gets peoples' attention. But it has a bad rap. #VelocityConf
The reality is that we all do it all the time. Responsible engineers test in prod, irresponsible engineers don't.

It's actually a false dichotomy; it's not a binary. You can test in production *and* before you reach production. #VelocityConf
Read 34 tweets
Advance slides in case anyone needs them (e.g. for accessibility reasons), for my #VelocityConf keynote! Featuring art by @emilywithcurls! drive.google.com/file/d/19_QS5a…

See you all at 9:05am sharp!
and here are some additional resources: I'll mention at the end of my talk: honeycomb.io/blog/toward-a-… and infoq.com/articles/produ… #VelocityConf
And you can hit up velocityconf.com/captions to see my words in realtime, even if you aren't here in person!

Just imagine me saying them alongside my slides ;) #VelocityConf
Read 3 tweets
It blew people's minds when I said "we literally sent 25% of our company to work the booth at #VelocityConf" when explaining why I couldn't livetweet as much this conference. Our booth duty, like everything else we do, is run through grit and tenacity.
We are literally throwing engineers, founders, anyone we can pull, into booth duty. We don't have a giant marketing or devrel machine (I wish we did).

All we have is a great product, and world-class experts working on it.
Come talk to @honeycombio at #VelocityConf. You might run into @maplebed, for instance. Or me. Or @mipsytipsy. In addition to the indomitable team of @dotpem and @jennitbd.
Read 3 tweets
.@gwenshap on running out of disk space: you can add more disk, or turn it off, change retention settings, and then back on.

the worst thing you can do is truncate the disk log with /dev/null while Kafka is running. Corruption!! #VelocityConf
@gwenshap When you're in a hole, first stop digging. If you don't know where the holes are, stop digging.

If you over-provision, upgrade to pick up bugfixes, feel comfortable asking for support, and don't "just tweak the parameters because"... you'll be better off. #VelocityConf
Subtle edge cases: if your disks are full but you discover it through an asynchronous flush... and it then crashes... and there aren't enough caught up leaders for quorum... data loss.

a human needs to decide what the new golden state should be after data loss. #VelocityConf
Read 18 tweets
Last night -- took 4 hours to find my airbnb, which I was locked out of; another 2 he til I got in (at 5:30a)

This morning -- locked in the cement basement for an hour w no signal

... San Jose hates me, your honor, and that's why I'm late for author signing @velocityconf 😩
let's not even get into last night, where I ended up in a hotel where I picked up my keys from a bulletproof glass window facing the street, and high tailed it home at 3 am after realizing my neighbor was... entertaining visitors, and her pimp outside kept calling to me #sanjose
(that's not even why I went home, actually... went home because there was no AC, and heeeeell no)

Anyway, my book signing will be during my ask the experts session. It's better this way. I'll have some unicorn cover stickers here by then. #VelocityConf
Read 3 tweets
Next at #VelocityConf, @aknin on being an SRE
Engineering and reliability are opposing forces, and we need a mix. 100% reliability allows for no change or improvement. #velocityConf
Once we measure reliability, we can create an error budget. Failure has a quantifiable range that’s ok - teams can move as fast as they want, if the error budget is not exceeded. #velocityConf
Read 8 tweets
The final keynote of the morning is my former colleague @aknin, on how to be an SRE (and no, it's not starting a new org structure)! [ed: I've reviewed this talk in advance and it is *killer*] #VelocityConf
@aknin He works with teams to understand what reliability means, and then to quantify that definition.

This requires SRE skills, development skills, and product/project management skills. #VelocityConf
We should first start by defining SRE. Not all of us have the same definition!

Engineering -> using scientific principles to design/build things.

But how do you apply science and design to reliability? #VelocityConf
Read 19 tweets
Opening #VelocityConf is @GoldbergChen (director of GKE/Istio) on using tech to scale your teams!
@GoldbergChen "Talent is the most valuable thing every company has, and happy teams build happy products." --@GoldbergChen #VelocityConf
Think about whether you're setting up both the team and the product for success when you make choices. #VelocityConf
Read 15 tweets
"There are only two things your organization should be spending time on: making your customers happy, or making your people happy.". -@lizthegrey at o11y meetup. #velocityconf
"CI/CD is great, and it's only the first step. We need to learn how to get our code into production faster, understand it better, and use the same tools for pre-prod and production"

(my phone camera broke so all I can do is selfies now, sorry)
speaking of which, here is my summary of San Jose today
Read 3 tweets
First tutorial of the day: “Move Fast and Learn from Incidents” with @lhochstein , @this_hits_home , and @nora_js along with a great crowd of TAs from Netflix, Slack, New Relic, and OSU! #VelocityConf
We are going to be role playing a few incident investigations during the session #velocityconf
A few things we’ll be looking for during these investigations which @lhochstein deems “gaps” falling into the following categories:
1) Tools
2) Operational expertise
3) Resource (people) gaps

#VelocityConf
Read 13 tweets
Final talk I'll be getting to at #VelocityConf before I dash to Toronto: @IanColdwater on improving container security on k8s.
@IanColdwater She focuses on hardening her employer's cloud container infrastructure, including doing work on k8s.

She also was an ethical hacker before she went into DevOps and DevSecOps. #VelocityConf
She travels around doing competitive hacking with CTFs. It's important to think like an attacker rather than assuming good intents and nice user personas that use our features in the way the devs intended things to be used. #VelocityConf
Read 36 tweets
My colleague @sethvargo on microservice security at #VelocityConf: traditionally we've thought of traditional security as all-or-nothing -- that you put the biggest possible padlock on your perimeter, and you have a secure zone and untrusted zone.
@sethvargo We know that monoliths don't actually work, so we're moving towards microservices. But how does this change your security model?

You might have a loadbalancer that has software-defined rules. And you have a variety of compartmentalized networks. #VelocityConf
You might also be communicating with managed services such as Cloud SQL that are outside of your security perimeter.

You no longer have one resource, firewall, loadbalancer, and security team. You have many. Including "Chris." #VelocityConf
Read 19 tweets
Leading off the k8s track today is @krisnova on migrating monoliths to k8s! #VelocityConf
@krisnova [ed: p.s. her ponies and rainbows dress is A+++]

She starts by providing a resources link: j.hept.io/velocity-nyc-2…

The problems we're solving:
(1) why are monoliths harder to migrate?
(2) Should you?
(3) How do I start?
(4) Best practices #VelocityConf
.@krisnova is a Gaypher (gay gopher), is a k8s maintainer, and is involved in two k8s SIGs (cluster lifecycle & aws, but she likes all the clouds. depending upon the day). And she did SRE before becoming a Dev Advocate! #VelocityConf
Read 29 tweets

Related hashtags

Did Thread Reader help you today?

Support us! We are indie developers!


This site is made by just three indie developers on a laptop doing marketing, support and development! Read more about the story.

Become a Premium Member ($3.00/month or $30.00/year) and get exclusive features!

Become Premium

Too expensive? Make a small donation by buying us coffee ($5) or help with server cost ($10)

Donate via Paypal Become our Patreon

Thank you for your support!