1. Build needlessly-complicated system 2. Impress engineering friends 3. Fail customers
-
-
- その他の返信を表示
-
@ThePracticalDev 4. Blame it on JavaScript - さらに表示
-
-
@ThePracticalDev Chapters 2 - 5,000: Docker -
-
@ThePracticalDev@mharrigan my current client is using postgres, mysql, mongodb, redis, Cassandra and neo4j in the same project. Srs. -
@gdh_gdh@ThePracticalDev@mharrigan "get *all* the CV buzzwords from a single project"-driven development? -
@skolima@mharrigan It's four different software firms with hilariously little oversight. I get to watch the sparks fly; fun!
-
-
@ThePracticalDev OH: Chapter 3: Creating scale issues while solving imaginary scale issues at scale -
@ThePracticalDev Cutest scaling issues ever. -
@ThePracticalDev@homphs step 2: choose an interpreted language that runs on another interpreter inside a VM, and has no thread/fork support -
@ThePracticalDev This triggers my PTSD from working with the pre 3.0 MongoDB. If I could only go back in time and stop myself. -
@ThePracticalDev@rzezeski Not a pic of a bikeshed? -
@ThePracticalDev also known as using that cool nosql db for your 5 users on production -
@ThePracticalDev Rofl! The number of times I encounter people trying to prematurely scale is like fighting a bear with imaginary Cubs. -
@ThePracticalDev That book is useless to me because my software needs to be at web scale. -
@ThePracticalDev@codehitchhiker the subtitle "At Scale" got me -
@ThePracticalDev Conference talk, youtube video, potato, patata. -
@ThePracticalDev@lattera and that's how we ended up running tomcat..in docker...on aws.. -
@ThePracticalDev@dlsniper chapter 127: what would aphyr do? -
@ThePracticalDev@jacobstanley Sounds like something you'd like :)
読み込みに時間がかかっているようです。
Twitterの処理能力の限界を超えているか、一時的な不具合が発生しています。もう一度試すか、Twitterステータス(英語)をご確認ください。