jeffrey-sherman

9 ms·

61.
A Settings Garbage Collector in 2 Shell Scripts(shermanonsoftware.com)
1 points by jeffrey-sherman 3y ago|0 comments
62.
Do the Hard Part First(shermanonsoftware.com)
2 points by jeffrey-sherman 3y ago|0 comments
63.
The Pause – Asking to Stop New Development for a Rewrite(shermanonsoftware.com)
1 points by jeffrey-sherman 3y ago|0 comments
64.
Computerizing India's Railways in the 1980s(youtube.com)
2 points by jeffrey-sherman 3y ago|0 comments
65.
by jeffrey-sherman 3y ago
I’d love to hear more about your experiences! I’m the author of the post and co-host of the never rewrite podcast. Last episode we discussed Khan Academy’s 3.5 year rewrite. https://youtu.be/LqAkIkNs1Ws?si=d3y6J2C6Q3T8qTyF
66.
by jeffrey-sherman 3y ago
Author of the post here - Lots of comments about the piece being a short opinion piece without evidence. Totally fair! If you’d like to learn more I have a podcast, https://www.neverrewrite.com/ Our latest episode is about
67.
Rewrites are Waterfall(shermanonsoftware.com)
60 points by jeffrey-sherman 3y ago|62 comments
68.
When a 33% Success Rate Outperforms 99.999%(shermanonsoftware.com)
2 points by jeffrey-sherman 3y ago|1 comments
69.
Scaffolding, Tests, and Throw Away Work(shermanonsoftware.com)
3 points by jeffrey-sherman 3y ago|0 comments
70.
SmileAndDial CRM – A Fable About Transforming Fundamental Constraints(shermanonsoftware.com)
2 points by jeffrey-sherman 3y ago|0 comments
71.
Transitioning from Microservices to a Monolith(youtube.com)
3 points by jeffrey-sherman 3y ago|0 comments
72.
Better in Every Way Is Impossible, Why Legacy Tech Will Not Go Away(shermanonsoftware.com)
1 points by jeffrey-sherman 3y ago|1 comments
73.
What's the opposite of rewriting your software?(shermanonsoftware.com)
2 points by jeffrey-sherman 4y ago|0 comments
74.
Scaling Your SaaS Like a Baker(shermanonsoftware.com)
1 points by jeffrey-sherman 4y ago|0 comments
75.
The C in CRM Grows Unbounded(shermanonsoftware.com)
2 points by jeffrey-sherman 4y ago|0 comments
76.
Never Rewrite, a Podcast Devoted to Software Evolution(neverrewrite.com)
2 points by jeffrey-sherman 4y ago|1 comments
77.
Code of Theseus – Does iterative delivery create a new system?(shermanonsoftware.com)
1 points by jeffrey-sherman 4y ago|0 comments
78.
Madison Square Garden, an Iteratively Upgraded Stadium(shermanonsoftware.com)
1 points by jeffrey-sherman 4y ago|0 comments
79.
Building Like the Yankees(shermanonsoftware.com)
1 points by jeffrey-sherman 4y ago|0 comments
80.
A low risk strategy to update your CRM's User Defined Field Pattern(shermanonsoftware.com)
2 points by jeffrey-sherman 4y ago|0 comments
81.
A brief history of User Defined Field patterns for CRMs – Part 3, Hybrid(shermanonsoftware.com)
1 points by jeffrey-sherman 4y ago|1 comments
82.
by jeffrey-sherman 4y ago
Exactly right!
83.
A brief history of User Defined Field patterns for CRMs – Part 2, NoSql(shermanonsoftware.com)
2 points by jeffrey-sherman 4y ago|2 comments
84.
A brief history of User Defined Field patterns for CRMs(shermanonsoftware.com)
1 points by jeffrey-sherman 4y ago|0 comments
85.
Cheerfully Going to Fail in Production(shermanonsoftware.com)
1 points by jeffrey-sherman 4y ago|0 comments
86.
Acceptable Beer Bellies in Your Codebase(shermanonsoftware.com)
1 points by jeffrey-sherman 4y ago|0 comments
87.
Is This a Quality Panel?(shermanonsoftware.com)
2 points by jeffrey-sherman 4y ago|0 comments
88.
How to break the “get me everything” cycle(leaddev.com)
13 points by jeffrey-sherman 4y ago|1 comments
89.
Punishing customer loyalty when crossing from startup to scaleup(shermanonsoftware.com)
1 points by jeffrey-sherman 4y ago|0 comments
90.
Iterable Delivery Framework: Chipping Away at the Blockers(shermanonsoftware.com)
1 points by jeffrey-sherman 4y ago|0 comments

More ›