A weekly changelog makes us go fast 🏃♂️
Apr 9, 2020
Given that as a super early stage startup, we're frequently stretched thin, we often wondered **does it make sense to maintain this changelog?** This was especially a big question early on, when we only had one customer and it could've been far easier to just show them any changes.
Exploring property-based testing
Jan 20, 2015
Prerequisite If you haven’t watched a presentation on property-based testing by John Hughes, please watch it – the presentation does a great job of explaining both: (i) what property-based testing is, and (ii) the power (nay, magic!) of property-based testing in finding hard-to-discover bugs.
Reid Draper, the primary author of Clojure’s test.check, describes the core idea behind property-based testing:
Instead of enumerating expected input and output for unit tests, you write properties about your function that should hold true for all inputs.
Don't drop the ring
Nov 18, 2014
If you are a Clojure newbie (“noob”) like myself, you may run into this issue. I am only writing this since it took me a lot longer to resolve this “issue” than it should have. My hope in writing this article is to help future noobs Googling for a solution to the same problem.
As it happens, I am currently developing a web app using compojure on top of ring. As I had done a couple times before, I made an uberjar to deploy the web app as a standalone server:
Delivering customer value
May 8, 2013
I am presently working on a pre-1.0 software product at VMware. It’s exciting time: rapid product development based on customer feedback, no support requests from customer issues in production, tremendous freedom as a standalone R&D organization, no legacy and/or compatibility issues to worry about, hopes as high as the Burj Khalifa, etc.
However, as a business, VMware obviously has plans to make revenue from our efforts. As we come close to the release milestone, some of our team members are curios about revenue expectation of our 1.
On the importance of shipping
Mar 8, 2013
Earlier today, our team was discussing a newly implemented feature during our bi-weekly sprint review meeting. The feature introduced a configuration knob that end users may adjust frequently. This knob was built atop our existing configuration management system, which required the software to be restarted for any change to take effect. This had been a known problem, however, as most prior configuration knobs led to infrequent adjustments, we had avoided fixing the root cause.