jeffrey-sherman

12 ms·

91.
Iterable Delivery Part 4: What Are the Blockers?(shermanonsoftware.com)
1 points by jeffrey-sherman 4y ago|0 comments
92.
Thinking through the implications of your iterable goals(shermanonsoftware.com)
2 points by jeffrey-sherman 4y ago|0 comments
93.
Defining your goal's characteristics in iterable ways(shermanonsoftware.com)
1 points by jeffrey-sherman 4y ago|0 comments
94.
Picking an iterative goal at a SaaS Scaleup(shermanonsoftware.com)
2 points by jeffrey-sherman 4y ago|0 comments
95.
A Framework for Getting Started with Iterative Delivery(shermanonsoftware.com)
1 points by jeffrey-sherman 4y ago|0 comments
96.
The only client experience you can offer, is the one you have today(shermanonsoftware.com)
1 points by jeffrey-sherman 4y ago|0 comments
97.
When your customers struggle with your interface, would they rather(shermanonsoftware.com)
2 points by jeffrey-sherman 4y ago|0 comments
98.
Moonshots vs. Baby Steps at a Scaleup: Who are you delivering for?(shermanonsoftware.com)
1 points by jeffrey-sherman 4y ago|0 comments
99.
The Opposite of Iterative Delivery – Do You Want to Be Erratic and Overwhelming?(shermanonsoftware.com)
1 points by jeffrey-sherman 4y ago|0 comments
100.
Dropdooms How Binding an Unbounded Reference Table Can Kill UI Performance(activecampaign.com)
1 points by jeffrey-sherman 5y ago|0 comments
101.
Build Allies By Asking “How did you solve it?”(shermanonsoftware.com)
1 points by jeffrey-sherman 5y ago|0 comments
102.
Racism In, Racism Out(shermanonsoftware.com)
2 points by jeffrey-sherman 6y ago|0 comments
103.
Links vs. Tags – asynchronous value building vs. a directed path(shermanonsoftware.com)
2 points by jeffrey-sherman 6y ago|0 comments
104.
AWS’s Elastic Load Balancer is a Strangler(shermanonsoftware.com)
112 points by jeffrey-sherman 7y ago|45 comments
105.
Probing Questions for Executives Approving a Rewrite(shermanonsoftware.com)
1 points by jeffrey-sherman 7y ago|0 comments
106.
How to tell the difference between a task you can automate, and one you should(shermanonsoftware.com)
1 points by jeffrey-sherman 7y ago|0 comments
107.
When automation is an expensive waste of time(shermanonsoftware.com)
2 points by jeffrey-sherman 7y ago|0 comments
108.
A Tale of Two Failures(shermanonsoftware.com)
1 points by jeffrey-sherman 7y ago|0 comments
109.
A starting guide to help think through a software rewrite(shermanonsoftware.com)
3 points by jeffrey-sherman 7y ago|0 comments
110.
Refactor your Pixel Tracking to survive a database outage(shermanonsoftware.com)
2 points by jeffrey-sherman 7y ago|0 comments
111.
Hooking Your SaaS's Reputation to Your Client's Performance(shermanonsoftware.com)
2 points by jeffrey-sherman 7y ago|0 comments
112.
Don't say I wouldn't have done it this way(shermanonsoftware.com)
2 points by jeffrey-sherman 7y ago|1 comments
113.
Making Link Tracking Scale – Part 2 Edge Caching(shermanonsoftware.com)
1 points by jeffrey-sherman 7y ago|0 comments
114.
It's Not Sabotage, They're Drowning(shermanonsoftware.com)
144 points by jeffrey-sherman 7y ago|101 comments
115.
Making Link Tracking Scale – Part 1 Asynchronous Processing(shermanonsoftware.com)
2 points by jeffrey-sherman 7y ago|0 comments
116.
A Cheesy Refactoring Analogy(shermanonsoftware.com)
1 points by jeffrey-sherman 7y ago|0 comments
117.
Database Is Not a Queue – A Live Example(shermanonsoftware.com)
1 points by jeffrey-sherman 7y ago|0 comments
118.
Scaling Bugs Are Different(shermanonsoftware.com)
1 points by jeffrey-sherman 7y ago|0 comments
119.
Ws for Software Developers(shermanonsoftware.com)
2 points by jeffrey-sherman 7y ago|0 comments
120.
Tactical API Obsolescence(shermanonsoftware.com)
1 points by jeffrey-sherman 7y ago|0 comments

More ›