Post 64098 by bbense@mastodon.technology
 (DIR) More posts by bbense@mastodon.technology
 (DIR) Post #63967 by fool@mastodon.technology
       2018-09-17T19:53:44Z
       
       0 likes, 0 repeats
       
       Working in tech, it's natural to despair at the state of the quality of work done. Unmanageable janky code, pathological product management, wasted time, Kafkaesque organizational impediments. What comforts me is the knowledge that all of this can be done in a way that actually works. It is possible to get it right.
       
 (DIR) Post #63968 by thatcosmonaut@knzk.me
       2018-09-17T19:54:30Z
       
       0 likes, 0 repeats
       
       @fool i imagine the first 50 years of bridge building were pretty bad too
       
 (DIR) Post #64098 by bbense@mastodon.technology
       2018-09-17T20:04:25Z
       
       0 likes, 0 repeats
       
       @thatcosmonaut @fool I think the difference between bridges and tech is that bridge engineers learn from failures. https://en.wikipedia.org/wiki/Tay_Bridge_disaster
       
 (DIR) Post #64102 by Otuk@mastodon.technology
       2018-09-17T20:04:48Z
       
       0 likes, 0 repeats
       
       @thatcosmonaut@foolI agree SW engineering is still lacking standards and standard components that make up a solution for any project no matter how many times we say plug and play, template, cookie cutter, containerized.For good or bad, there is a huge diversity in options, and it drives artisanal one of a kind solutions and coding.
       
 (DIR) Post #64128 by thatcosmonaut@knzk.me
       2018-09-17T20:06:51Z
       
       0 likes, 0 repeats
       
       @bbense @fool another difference is that bridges wont immediately collapse if not propped up by a global system of financialized capital