index.html 9.2 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221
  1. <!DOCTYPE html>
  2. <html>
  3. <head>
  4. <title>David Ventura - resume</title>
  5. <link rel="stylesheet" href="css/style.css">
  6. <link href="https://fonts.googleapis.com/css?family=Lato|Open+Sans|Montserrat:400,400i,600,700,800&display=swap" rel="stylesheet">
  7. </head>
  8. <body>
  9. <header>
  10. <div class="resume-title">
  11. <h1>David Ventura</h1>
  12. <h2>
  13. SysAdmin, Devops & Dev
  14. <small>Jack of all trades</small>
  15. </h2>
  16. </div>
  17. <div class="personal-info">
  18. <p>
  19. Argentinian living in The Netherlands <br/>
  20. <a href="mailto:davidventura27@gmail.com">davidventura27@gmail.com</a> <br/>
  21. <a href="https://github.com/davidventura">github.com/DavidVentura</a> <br/>
  22. <a href="https://gitlab.com/davidventura">gitlab.com/DavidVentura</a> <br/>
  23. <a href="https://blog.davidventura.com.ar">blog</a> <br/>
  24. </p>
  25. </div>
  26. </header>
  27. <section class="experience-category">
  28. <h2 class="experience-title">
  29. Work Projects
  30. </h2>
  31. <div class="work-experience">
  32. <h3 class="company-name">
  33. <small>2018 - current</small>
  34. Optiver
  35. <small class="position">Sysadmin - Tooling developer</small>
  36. </h3>
  37. <p>
  38. Enforced operational commitments from development teams to bring down application errors to monitorable state.
  39. <ul>
  40. <li>
  41. Overhaul compliance related backup system (300TB+)
  42. </li>
  43. <li>
  44. Deployment system for production services (11k services, 860 servers)
  45. </li>
  46. <li>
  47. Linux-on-windows initiative and platform deployment to standardize the production API across the existing services
  48. </li>
  49. <li>
  50. Log and event analysis to quickly detect production related incidents
  51. </li>
  52. <li>
  53. Redesigned and implemented market data permissioning system
  54. </li>
  55. <li>
  56. (Currently) Redesigning server deployment
  57. </li>
  58. <li>
  59. Mentored colleagues, healping them transition from an old-school sysadmin position to a tooling development position
  60. </li>
  61. </ul>
  62. </p>
  63. </div>
  64. <div class="work-experience">
  65. <h3 class="company-name">
  66. <small>2014 - 2018</small>
  67. Especificos Buenos Aires
  68. <small class="position">Sysadmin - Tooling - Backend dev - Frontend dev - Embedded - Networking</small>
  69. </h3>
  70. <div class="company-project">
  71. <h4>Live-streaming Platform</h4>
  72. <p>
  73. The objective of this project was to create a complete pipeline for live video streaming, all the way from the physical cameras in the classroom to the software used by the alumni. A few interested points covered by the project:
  74. <ul>
  75. <li>
  76. Embedded linux systems for the video cameras (raspberry pi), audio mixer and slide system
  77. </li>
  78. <li>
  79. Live audio mixing of remote and local speakers
  80. </li>
  81. <li>
  82. Time syncing across video sources to prevent frame drift, using PTP
  83. </li>
  84. <li>
  85. Slide software that allows presenter to draw on slides and alumni to ask questions to the presenter
  86. </li>
  87. </ul>
  88. </p>
  89. </div>
  90. <div class="company-project">
  91. <h4>Online training platform</h4>
  92. <p>The objective of this project was to create a ‘forum’-like website to post the videos with the corresponding text material, allowing the students to communicate with each other.</p>
  93. </div>
  94. <div class="company-project">
  95. <h4>
  96. Billing System
  97. </h4>
  98. <p>This project manages most of the finances of the company and some extras:</p>
  99. <ul>
  100. <li>Billing, receipts (AFIP), shipping labels, e-commerce, stock and supplies</li>
  101. <li>Document scanning, printint, security cameras, certificate generator and monthly reports</li>
  102. </ul>
  103. </div>
  104. </div>
  105. <div class="work-experience">
  106. <h3 class="company-name">
  107. <small>2014-2018</small>
  108. Freelancing
  109. </h3>
  110. <div class="company-project">
  111. <h4>
  112. Streamall (netflix 'clone')
  113. <small class="position">Sysadmin - Backend dev - Frontend dev - Tooling</small>
  114. </h4>
  115. <p>
  116. In this project I designed and implemented a system that allowed hundreds of users to access thousands of long-form videos on demand, deployed on a physical cluster in a colocation with high availability and a smart caching system designed to keep 'hot' items in an SSD cache, while a massive store was on tier-3 disks.
  117. The project included:
  118. <ul>
  119. <li>
  120. Distributed transcoding of the content to a multitude of formats supported by the customer's devices.
  121. </li>
  122. <li>
  123. Web-ui for the administrator to handle users, API keys and content metadata
  124. </li>
  125. </ul>
  126. </p>
  127. </div>
  128. <div class="company-project">
  129. <h4>
  130. News parser (PYMNTS.com)
  131. <small class="position">Sysadmin - Backend dev - Frontend dev - Tooling</small>
  132. </h4>
  133. <p>
  134. The main purpose of this project was the automatization of data scraping from multiple news sources.
  135. </p>
  136. <p>
  137. The data is gathered by polling the sources in a parallelized manner every set amount of time, validated against a set of keywords (with associated per-source weights) and stored in a database.
  138. </p>
  139. <p>
  140. The sources and keywords can be managed by the users via a web interface; they also decide which matching articles are not useful and tag them as such, every month the weights and keywords get reevaluated based on ‘useless’ articles.
  141. </p>
  142. <p>
  143. We also have a dashboard displaying metrics, keywords, per-source matches and per-keyword matches.
  144. </p>
  145. </div>
  146. <div class="company-project">
  147. <h4>
  148. Multi-language interpreter to extract embedded SQL queries
  149. </h4>
  150. <p>
  151. We had a lot of old applications that had embedded SQL queries and the company had to migrate from Oracle 8 to Oracle 11. To achieve that, we had to analyze ALL the embedded queries so we created an parser for VB6, VB.NET, C#, ASP.NET and Java.
  152. </p>
  153. </div>
  154. </div>
  155. </section>
  156. <section class="experience-category">
  157. <h2 class="experience-title">
  158. Bonus tracks
  159. </h2>
  160. <div class="bonus-track">
  161. <p>
  162. Some of my personal projects. You can find more at my <a href="blog.davidventura.com.ar">blog</a>
  163. <ul>
  164. <li>
  165. Reverse engineered the android application to report poorly parked cars provided by the government to automate submissions of people parking in my garage
  166. </li>
  167. <li>
  168. Proposed a system (and proof-of-concept) to the highway authorities to catch speeding cars in freeways/highways using OpenCV to detect the license plates
  169. </li>
  170. <li>
  171. IoT projects:
  172. <ul>
  173. <li>Wrote a small IOT framework in MicroPython, which I use for my custom devices</li>
  174. <li>Used said framework to control my nightlamp with my kindle, measure ambient humidity/temperature, switch TV input sources, etc.</li>
  175. </ul>
  176. </li>
  177. </ul>
  178. <li>
  179. Currently writing a set of tools to handle my 3d-printer in better ways (emitting consistent gcode, cura plugin)
  180. </li>
  181. <li>
  182. Currently writing a video pipeline to detect and flag motion detection with my home security cameras.
  183. </li>
  184. </p>
  185. </div>
  186. </section>
  187. <section class="experience-category">
  188. <h2 class="experience-title">Lab Experience</h2>
  189. <div class="lab-experience">
  190. <p>
  191. Along with my normal projects I maintain a 'lab' to both host my projects and learn about new or interesting tech. Some items of note in the lab:
  192. <ul>
  193. <li>
  194. ARM Cluster: load-balancing LXC cluster on multiple physical ARM single-board-computers of (slightly) different architectures (armv6, AArch64) with live container migration using CRIU
  195. </li>
  196. <li>
  197. Jenkins for automated tests and tricky builds (one of the projects is Android-Windows-Linux)
  198. </li>
  199. <li>
  200. My physical router is fully deployed from the lab with ansible.
  201. </li>
  202. <li>
  203. All containers and VMs are fully deployed with ansible
  204. </li>
  205. <li>
  206. Backup system (automated ping for offline backups, daily delta and weekly snapshots uploaded to different zones, via different mechanisms)
  207. </li>
  208. </ul>
  209. </p>
  210. <p>
  211. All of this is monitored with generic tools (telegraf, influx, grafana, email) and also hosts some generic tooling for itself (squid, apt-cacher, git, backups)
  212. </p>
  213. </div>
  214. </section>
  215. </body>
  216. </html>