Striving to get to the only conversation that matters: How do I make my customers bad-ass?
Winnipeg, Manitoba
Joined April 2013
- Tweets400
- Following546
- Followers83
- Likes784
Paul Everton retweeted
Hi! My name is Mariana, an experienced Accountant and Bookkeeper with over 8 years of experience in accounting. I'm looking for any job opportunities related to accounting and bookkeeping in the Ottawa area or remote in Canada. I have an open work permit. Please RT. Thank you!
Paul Everton retweeted
This is the real goal of CI/CD -- to shrink the software lead time to an interval short enough that human learning systems (dopamine, adrenaline) can usefully map to the feedback loop of writing and shipping code.
(and then of course there's @darklang, the hot stove of software)
You’re unable to view this Post because this account owner limits who can view their Posts. Learn more
Paul Everton retweeted
There is no, has never been, and will never be any environment that looks just like prod.
🌺Only production is production.🌺 Test in prod or live a lie.
Paul Everton retweeted
I'd rather spend $3000 on someone who can use it than wasting it on Twitter ads, so here we go
🎉New Year's Giveaway🍾
I'm giving away a new 🍏MacBook Pro 16" to a random person who retweets this tweet
👩🎨 Make something cool w/ it
(you have to follow because I want followers)
Paul Everton retweeted
over the last couple years I've shifted from "we have to teach SRE stuff to these wild engineers" to "assume the engineers know what the right thing to do is and empower them to do it" and this feels way better
Paul Everton retweeted
The whole “to deploy or not to deploy on a Friday” discussion (which I completely missed yesterday since I’d misplaced my phone) conflates a “deploy” with a “release”.
One of the most efficient tactics to manage and mitigate risk is to decouple the two. teapawt.net/copyconstruct/status/1…
Mandatory reading - these two blog posts from the folks at Turbine Labs (RIP) about the perils of conflating "deploy" and "release". I also referenced these ideas in my post on testing in production (medium.com/@copyconstruct/te…)
blog.turbinelabs.io/deploy-n… and blog.turbinelabs.io/deploy-n…
Paul Everton retweeted
Best of 2018 in tech talks.
It’s a list of 30 of my favorite talks covering pretty diverse topics - concurrency in Kotlin, writing an OS in Rust, consistency without distributed consensus, autonomous testing, fast safe mutable state and a lot more. bit.ly/2Sp4ggp
Paul Everton retweeted
A polyrepo forces team responsibility and isolation as the default. A monorepo forces shared responsibility and visibility as the default. You will build equivalent amounts of tooling. At scale, harder to get teams to shared responsibility and visibility medium.com/@adamhjk/monorepo…
Paul Everton retweeted
I finally hit my monorepo discussion limit, so I present you with "Monorepos: Please don't!" Enjoy. 😃
medium.com/@mattklein123/mon…
Paul Everton retweeted
Yes!!!
Norms and culture do the heavy lifting in a healthy eng team. So this is exactly the way to think about it -- not "what rule do we pass", but "how do we make {blamelessness,instrumentation,oncall} cool and aspirational?"
Paul Everton retweeted
I like this heuristic, and have a few which are similar in intent to it:
Paul Everton retweeted
Excited to finally talk about @bevylabs community events product spun out of @StartupGrind last year. We've raised $6M from some great people. venturebeat.com/2018/06/19/b…
Paul Everton retweeted
Great tip for #appsec teams by @shehackspurple - ALWAYS Push left and get security added to your project as early as possible! @securityfest #secfest – at Gothenburg, Sweden
Paul Everton retweeted
RT if you too have a box like this in your house
ALT It's a box brimming with cables
Paul Everton retweeted
Calling all #midwifery and #obstetrics professionals!
We need your help to make our free obstetrics date calculator app #PregoWheel available to everyone in the world by translating it into YOUR native language. Interested? jeffreyfulton.ca/projects/pr…
Paul Everton retweeted
Wrote down all of my thoughts on testing microservices -
the tradeoffs, antipatterns, what I call the "step up rule", how to test with service meshes, testing in production vs pre production testing, as well as a new test pyramid for distributed systems
bit.ly/2lpyVI5
Paul Everton retweeted
Really enjoying this conversation on testing lately. Testing starts when you write the code, and ends when you delete the code or decommission it from production.
The latest terrific salvo from @copyconstruct: medium.com/@copyconstruct/te… – at San Francisco, CA
Paul Everton retweeted
My belief was that integration testing in “test” clusters is useless and should die - live traffic testing is the future. TIL Facebook's been doing it for a long time. bit.ly/2BQIuWz
With service meshes unlock so much potential for better testing to us unwashed masses.
