about

the short version

physicist and chemist turned software engineer. currently building side projects and documenting the journey.

the longer version

i studied physics. it wasn’t enough, so i decided to study chemistry as well. graduated from both simultaneously and eventually realized that while science is fascinating, building software scratches an itch i didn’t know i had.

so i did what any reasonable person would do - took a coding bootcamp. unlike most bootcamp stories, i was actually somewhat decent at it. that, combined with a friend who helped me get my foot in the door, landed me my first dev job.

started with javascript, aws, and serverless stuff. the usual starter pack.

then came an opportunity at adidas (yes, the shoe company). they had a headquarters in spain and i thought that might be cool. plus, employee discounts on shoes? sign me up.

somehow got hired for a position that required 3+ years of experience when i had less than one. classic imposter syndrome fuel.

at adidas, it was javascript, endless agile ceremonies, bureaucracy, and shoes. lots of shoes. oh, and that one time i broke the entire product exchange service worldwide for a weekend. good times.

then i discovered go - simpler than javascript, more performant than javascript, basically better than javascript in almost every way that mattered to me.

tried to get something going with go at adidas, but you know how it is with large corporations. change moves at glacial pace.

so i found myself at dorna, the company behind motogp, where they were using go. actually, i should say “we” because i’m still there. it’s been a wild ride learning from some seriously talented engineers.

but because i’m incapable of being satisfied, i started building side projects. one of those eventually evolved into something i might actually release someday, if i ever get around to finishing it.

what’s with this blog?

this is my engineering journal. it’s partly to document what i learn, partly to share with others, and partly to keep myself accountable as i build in public.

you’ll find:

  • technical deep dives into go, apis, and distributed systems
  • the unfiltered journey of building a saas product from scratch
  • occasional rants about technology choices
  • zero content about the oxford comma or capital letters

get in touch

krtffl.dev

physicist → chemist → dev


who is this guy and why should you care?