Rob Styles (@mmmmmrob) header
Rob Styles (@mmmmmrob) profile picture

Founder at Returnable. https://nitter.gq/t.co/DjOXlfwpEB Previously Day Out With The Kids, Meducation, Talis, Egg. He/him

UK
Joined February 2007
Photo by Rob Styles (@mmmmmrob)Photo by Rob Styles (@mmmmmrob)Photo by Rob Styles (@mmmmmrob)Photo by Rob Styles (@mmmmmrob)Photo by Rob Styles (@mmmmmrob)Photo by Rob Styles (@mmmmmrob)Photo by Rob Styles (@mmmmmrob)Photo by Rob Styles (@mmmmmrob)Photo by Rob Styles (@mmmmmrob)Photo by Rob Styles (@mmmmmrob)
Rob Styles retweeted
Fine. I’ll try Mastadon. Who all is there so I can follow? Drop your handle below! mstdn.social/@briannawu
59
8
1
142
So, the next time someone thinks they're being smart by telling you they "should have stayed in France"... here's the @JCWI_UK 5-step guide to responding, which doesn't involve pointing out how deeply they are lacking in either humanity or imagination...
212
3,029
515
7,499
Great article: "These days the Pre-Integration Review, carried out on a Pull Request is the most common mechanism for a code review, to the point that many people witlessly consider that not using pull requests removes all opportunities for doing code review." 1/
This Post is from an account that no longer exists. Learn more
1
1
14
Literally an exact graph of my programming career. Thankfully at the bottom right these days. Man did I ever overengineer some stuff in my early days.
1
6
Last week, we at @exercism_io launched an exciting new feature: a Dig Deeper section for exercises. @iHiD explains this new feature in youtube.com/watch?v=_-qYFe0a… For an example, check out the Dig Deeper section for the C# track's reverse-string exercise: exercism.org/tracks/csharp/e…
3
2
The only reason that Agile is faster is that we don't waste time building stuff nobody wants. There's nothing inherently faster in the approach. Sutherland's "twice the work in half the time" is pure BS.
This Post is from an account that no longer exists. Learn more
12
21
89
If you can’t run the suite after every new line of code or every refactoring, and you can’t merge/rebase with everyone else’s several times an hour, then you don’t know anything is wrong until after you’ve accumulated a bunch of problems in a bunch of places.
1
1
2
"I'm putting together my quotes, thoughts and notes on the idea that Frameworks harm the maintainability of the software you build in that framework" berk.es/2022/09/06/framework…
Product vs Engineering "Team members align themselves with their management structure or functional leadership as their primary identity, instead of their business or customer value stream,making it easier for teams to assume an “us” versus “them” posture" martinfowler.com/articles/bo…
web dev does not require a compile step and there are a tonne of downsides to adding one to your workflow
1
4
2
48
Any web server (or cloud function) that is capable of rendering an HTML string can include Custom Elements. (HTML elements defined by you.) If there is a <script> with customElements.define then any Custom Elements in the HTML will be upgraded. This is progressive enhancement.
2
1
21
Rob Styles retweeted
Your regularly-scheduled fleet week comic:
1
1
5
I posted a few of Deming's "14 points" (from "Out of the Crisis"; 1982) the other day. Pretty much all of these are relevant today in every software organization. Let's look at the whole list 👇 1/18
19
83
9
322
Arguably Philip K. Dick's worst novel
223
7,826
325
51,141
Rob Styles retweeted
If you have an Apple M1 or M2 and don't take advantage of its GPU, I'm about to change your life. These instructions allow TensorFlow to use your GPU: 1 of 10
146
864
36
6,230
Keep flipping a coin until you get the sequence HTH or HHH. Which is more likely to come first: HHH, HTH, or equally likely?
19
9
2
66
Rob Styles retweeted
Naming is hard, so we should just use arbitrary names and try to keep them straight in our heads. Custom types take effort so we should deeply nest native types and try to remember what each subscript means. Code is hard, so transfer more burden to heads? No thank you.
3
12
4
52
Keep test coverage high and maintenance costs low: * Lots of unit tests. Fast, $ * Some integration tests. Slow, $$ * Not too many E2E functional tests. Slowest, $$$
1
14