Software

  • At Olvy we built a tool that extracted user feedback from all customer interactions, ran it through an analysis and enrichment pipeline, and generated beautiful reports for the user. At least, that’s what our marketing focused on. The overall product did many things (one of the reasons we failed, will discuss this in later posts),…

  • I love languages with a type system and compilation—the confidence of “if it compiles, it’ll work” is worth every penny (<3 Golang) I first heard about these terms when I was in college, and it has been something I always think about when designing systems. Essentially, it’s a derivation of the age old programming adage…

  • You have been working on building a wonderful piece of software, that people actually love using. It solves a problem, and people would be really upset if it went away tomorrow. You’ve finally achieved product market fit at this point. Things are going great. There’s money hitting your bank. People never get tired of singing…

  • I was first introduced to programming in third standard with PC Logo. I still remember FD50, RT90, and maybe if I open it up I’ll recall how to draw a circle. I enjoyed it, but didn’t think much of it, and moved to my other interests like breaking down remote controlled cars, modifying them with…

  • It’s overwhelming. I’m someone who finds code in huge projects overwhelming. Understanding what the people before you have written down. The kind of complexity that would be embedded this codebase. Every line of it must be battle tested, and I have to add new code to it! NOOOOOOOO! There has to be a way to…

  • Engineers are objective people. Right brained as some of you might like to call them. In the last 14 months of starting my full-time job, and three internships at amazing startups before it, I’ve learned different. I assumed the decisions people made about the frameworks or technologies they use in their products must be a…