Engineering for Engineering's Sake

Engineering for Engineering's Sake

Code is a not an asset. Technology is not the solution to your company problems. And engineering for engineering's sake is not the answer.

B5009f255a6f0c386d40d6143948df8e?s=128

Mindaugas Mozūras

May 05, 2016
Tweet

Transcript

  1. ENGINEERING FOR ENGINEERING’S SAKE

  2. MMOZURAS CODINGFEARLESSLY.COM MMOZURAS

  3. None
  4. VINTED

  5. MAKE SECOND-HAND THE FIRST CHOICE WORLDWIDE

  6. None
  7. ENGINEERING IS FUN

  8. None
  9. READY TO STUDY SOMETHING SERIOUS

  10. WAIT A SEC.

  11. None
  12. ENGINEERING AT WORK IS NOT ALWAYS FUN (YES, EVEN AT

    VINTED)
  13. ENGINEERING AT HOME IS ALWAYS FUN

  14. None
  15. None
  16. HOW DO I ENGINEER? BTW, NOT A PIC OF MY

    HOME CASTLE
  17. PHP postgresql

  18. RUBY RAILS MYSQL BACKBONE

  19. ELIXIR PHOENIX RETHINKDB REACT

  20. I CAN BE A MAGPIE (SOMETIMES)

  21. I LOVE TO DO ENGINEERING FOR ENGINEERING’S SAKE

  22. SAME MINDSET AT WORK

  23. None
  24. None
  25. HOW TO THINK ABOUT ENGINEERING?

  26. REDIS’ING FEED

  27. 2013

  28. PEER TO PEER

  29. PEER TO PEER MARKETPLACE

  30. PEER TO PEER MARKETPLACE NEEDED A FEED

  31. VINTED

  32. None
  33. PICKS FOLLOWED (BRANDS/MEMBERS) SUGGESTIONS

  34. None
  35. REDIS IS A PERFECT FIT!

  36. REDIS SORTED SETS ARE A PERFECT FIT!

  37. MYSQL MEMCACHED REDIS +

  38. None
  39. MEMBERS ARE HAPPY!

  40. WHAT ABOUT ENGINEERS?

  41. None
  42. OOPS…

  43. FEED TECHNICAL DEBT

  44. FEED TECHNICAL DEBT

  45. REDIS TECHNICAL DEBT

  46. DEBT ISSUE OPENED: MARCH, 2014

  47. MIGRATION TO REDIS CLUSTER: SEPTEMBER, 2015

  48. 2010

  49. PEER TO PEER

  50. PEER TO PEER MARKETPLACE

  51. PEER TO PEER MARKETPLACE NEEDED A FEED

  52. None
  53. None
  54. None
  55. REDIS IS A PERFECT FIT!

  56. MYSQL MEMCACHED REDIS +

  57. MYSQL MEMCACHED REDIS +

  58. ETSY CHOSE MEMCACHED

  59. MEMBERS ARE HAPPY!

  60. ENGINEERS?

  61. THEY JUST MOVED ON TO WORK ON OTHER STUFF

  62. None
  63. REDIS VS. MEMCACHED

  64. SHININESS & STACK

  65. EXCITING VS. BORING

  66. None
  67. None
  68. None
  69. None
  70. 2009 VS. 2003

  71. TOOLS

  72. INFORMATION

  73. I KNOW THAT I KNOW NOTHING

  74. None
  75. LET GOOGLE/FACEBOOK/AMAZON FIGURE IT OUT

  76. NEW TO STACK VS. PART OF STACK

  77. KNOWLEDGE

  78. WAIT, WHAT SHOULD I USE AGAIN?

  79. OPERATIONS

  80. FEED 2.0? WHERE’S REDIS?

  81. DON’T ADD MORE UNLESS YOU REALLY REALLY REALLY REALLY NEED

    IT
  82. REDIS VS. MEMCACHED

  83. SHIPPING IS FUN

  84. SHIPPING IS MORE FUN

  85. SHIPPING IS FUNNEST (IS THAT A REAL WORD?)

  86. USEFUL BRIDGE, EH?

  87. THE GOAL IS EXCITING PRODUCT

  88. NOT THE “RIGHT” TOOL FOR THE JOB

  89. NOT ENGINEERING FOR ENGINEERING’S SAKE

  90. USE BORING CODE, TECH, ENGINEERING (AND EXCITING, SOMETIMES)

  91. OPTIMIZE COMPANY-WIDE SOLVE PROBLEMS WITH WHAT YOU ALREADY HAVE

  92. USE BORING & OPTIMIZE COMPANY-WIDE

  93. THANKS! MMOZURAS MMOZURAS