|
@markdalgleish | |||||
|
Developers: *Build terrible monolith*
"This isn't working. Let's try something else"
Developers: *Build terrible microservices*
"Wait—this isn't working either."
|
||||||
|
||||||
|
Laurie Voss
@seldo
|
31. sij |
|
If I were a developer I would simply not build bad software.
|
||
|
|
||
|
Mark Dalgleish
@markdalgleish
|
1. velj |
|
Developers: pic.twitter.com/VOJmrUQ8iy
|
||
|
|
||
|
Tim Myers
@denvercoder
|
31. sij |
|
I once worked at a place that wanted to build a “super-lean” infrastructure. So we had 10 micro services. But alas, they were having trouble communicating with each other so we combined a few and we had 5 micro services (we adapted, we were agile).
|
||
|
|
||
|
Tim Myers
@denvercoder
|
31. sij |
|
Well those five micro services were hard to maintain so we realized we only needed micro services for the “important” stuff so we then had 2 micro services.
|
||
|
|
||
|
André Scar 🦁
@andrewmat
|
31. sij |
|
Software engineering is just a infinite loop of separating things to bundle them together
|
||
|
|
||
|
Stephan H. Wissel
@notessensei
|
31. sij |
|
LEGO, do I hear Lego? Progression is from Duplo to basic 8dot blocks always with the goal in mind to build the next Death Star
|
||
|
|
||
|
Adam Argyle
@argyleink
|
31. sij |
|
Microlith is the word you're looking for 😋
|
||
|
|
||
|
Resi “sad Tifosi noises” Respati
@resir014
|
1. velj |
|
*Monoservices
|
||
|
|
||
|
Michael Timbs
@michael_timbs
|
31. sij |
|
What is the best architecture for terrible code then? Chances of me getting good at this coding thing are small so need architecture to save me
|
||
|
|
||
|
Stuart Jones
@horus_kol
|
31. sij |
|
single file application, no classes
|
||
|
|
||