Software is a messy business indeed.https://twitter.com/atomicthumbs/status/1032939617404645376 …
If it ain't broke, I'll fix it!
I'm porting Linux to Apple Silicon Macs at @AsahiLinux.
http://patreon.com/marcan | http://github.com/sponsors/marcan
You can add location information to your Tweets, such as your city or precise location, from the web and via third-party applications. You always have the option to delete your Tweet location history. Learn more
Add this Tweet to your website by copying the code below. Learn more
Add this video to your website by copying the code below. Learn more
By embedding Twitter content in your website or app, you are agreeing to the Twitter Developer Agreement and Developer Policy.
| Country | Code | For customers of |
|---|---|---|
| United States | 40404 | (any) |
| Canada | 21212 | (any) |
| United Kingdom | 86444 | Vodafone, Orange, 3, O2 |
| Brazil | 40404 | Nextel, TIM |
| Haiti | 40404 | Digicel, Voila |
| Ireland | 51210 | Vodafone, O2 |
| India | 53000 | Bharti Airtel, Videocon, Reliance |
| Indonesia | 89887 | AXIS, 3, Telkomsel, Indosat, XL Axiata |
| Italy | 4880804 | Wind |
| 3424486444 | Vodafone | |
| » See SMS short codes for other countries | ||
This timeline is where you’ll spend most of your time, getting instant updates about what matters to you.
Hover over the profile pic and click the Following button to unfollow any account.
When you see a Tweet you love, tap the heart — it lets the person who wrote it know you shared the love.
The fastest way to share someone else’s Tweet with your followers is with a Retweet. Tap the icon to send it instantly.
Add your thoughts about any Tweet with a Reply. Find a topic you’re passionate about, and jump right in.
Get instant insight into what people are talking about now.
Follow more accounts to get instant updates about topics you care about.
See the latest conversations about any topic instantly.
Catch up instantly on the best stories happening as they unfold.
Grady Booch Retweeted site specific carnivorous occurrence
Software is a messy business indeed.https://twitter.com/atomicthumbs/status/1032939617404645376 …
Grady Booch added,
My initial reaction is judgment of Tesla. But I know that I have been guilty of cutting corners myself, and that many companies I've worked with are in a similar situation as well. It's easy to point and laugh at someone else's dirty laundry, harder to admit that we have our own.
The important lesson that I take away: momentum is real.When we cut corners early on, rarely do we go back to fix it. The flood pushes us forward.
Completely agree! Sacrificing quality to meet deadlines is hardly a Tesla only phenomenon. Been there done that!
It's called technical debt. Everyone has it, but if you let it spiral out of control, you end up paying in the long run. A company that does not keep technical debt under control will eventually suffer the consequences.
Momentum might push you forward, but there comes a point when you're running on fumes. Eventually you do need to go back and fix the mess, and the more you wait, the exponentially worse it gets.
The difficulty, as with many systems, is that there's not a tight feedback loop for tech debt. Consequences occur at a time so far removed from the initial debt creation that there's not always a clear link in our minds. We tend to think our immediate problems have recent causes.
One way is to not push your employees to work 14 hours a day, 7 days a week, for extended periods of time, and to have a performance review process that isn't based on cutthroat competition. If you *let* your employees have spare time to go back and fix messes, (some) will.
I know I did, when I worked for $BigCo. I took over some legacy crap and rewrote it, pushed forward with security-oriented cleanups, etc. And people were supportive and I got plenty of kudos (and even bonuses) for it.
Fun story: one such legacy system was a thing a huge portion of the company depended on and was run by one (not very likable) dude. He left, system broke, manager was gone, manager's manager forgot her key card. I found out it was insecure anyway so I basically hacked into it.
Then I re-reployed it properly, closed the holes, fixed some showstopper bugs, recruited someone to join as a co-owner (so I wasn't a SPOF), then started a rewrite from scratch to improve a lot of flakiness and performance. Stuff needed to get done so I did it.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.