3 ms·

Say, for example, that my "side-project" was a HIPAA-compliant SAAS-software tool for doctors that they relied on every day (24x7). It needed to be deployed acr

by ci5er 10y ago

Say, for example, that my "side-project" was a HIPAA-compliant SAAS-software tool for doctors that they relied on every day (24x7). It needed to be deployed across multiple availability zones, and the team needed to be "on-call" for whatever didn't work, whenever it didn't work? How would that, for example, square with doing it in parallel with a 9-5? Or, are you talking about doing a project that people don't really really need? I have to imagine the failure rate of pushing a product that people don't need would be high, and the ability to support a product that they do need would not be compatible with the side-project concept. Am I wrong in thinking this?

robbiep 10y ago
If your side project is a HIPAA compliant SAAS tool for doctors, than it's hardly an MVP, so it's probably a poor choice for a side project. However, if you build software for doctors that avoids the regulatory compliance problems, then get it expanded out to 14 hospitals, then raise, then have staff, you can then go back and do that HIPAA compliant SAAS solution that you initially wanted to. Which pretty much describes my path over the last 3 years
- ci5er 10y ago
  I get your point, but getting it regulatorily compliant seemed (to me, at the time) easier than just dodging the question. A pain in the yatkova, to be sure, but it made sales easier to just hand them my basic-docs book (or fill out the questionairre) and say 'yes', 'yes', 'yes', than to fight with the provider's issues with their upstream issues. If you were able to dodge that, then, salute! EDIT: And, I will admit, there has been an amount of conflation of the term 'side-project', and 'startup' and 'mvp' and 'project' and 'product' over the (esp. last two) years that confuses me from time to time. I often lose the thread on context. My apologies if my comments reflect my lack of appropriate modern contextual understanding.
- deleted 10y ago
  [deleted]

by ci5er 10y ago

robbiep 10y ago

If your side project is a HIPAA compliant SAAS tool for doctors, than it's hardly an MVP, so it's probably a poor choice for a side project. However, if you build software for doctors that avoids the regulatory compliance problems, then get it expanded out to 14 hospitals, then raise, then have staff, you can then go back and do that HIPAA compliant SAAS solution that you initially wanted to. Which pretty much describes my path over the last 3 years

ci5er 10y ago
I get your point, but getting it regulatorily compliant seemed (to me, at the time) easier than just dodging the question. A pain in the yatkova, to be sure, but it made sales easier to just hand them my basic-docs book (or fill out the questionairre) and say 'yes', 'yes', 'yes', than to fight with the provider's issues with their upstream issues. If you were able to dodge that, then, salute! EDIT: And, I will admit, there has been an amount of conflation of the term 'side-project', and 'startup' and 'mvp' and 'project' and 'product' over the (esp. last two) years that confuses me from time to time. I often lose the thread on context. My apologies if my comments reflect my lack of appropriate modern contextual understanding.
deleted 10y ago
[deleted]