The web app somehow made its way to him! He sent me an extremely endearing message that it was fun to see his 2yo grandson using it! (Craig had originally made Kid Pix for his son who is now a graphic, ui, and ux designer). I let him know I made this port for my own daughter as a pandemic-project.
With Sqreen's acquisition, the list's previous home unfortunately redirects the their acquisition announcement. We're grateful that they released the list under CCA and we look forward to keeping it updated and relevant to startups on beginning their infosec journeys.
After making the rounds last week and getting some feedback on our tool, we wanted to show HN what we wrote that catches the backdoors that Salesforce's Endgame (https://news.ycombinator.com/item?id=26154038) targets. We would love to get your feedback and we hope you find it useful.
> For me it was always an uphill battle to sell the need of security
60+ ppl is pretty far along where other security aspects besides infosec also start showing up (e.g. securing employee computers, etc). Was this because tech-debt in general wasn't a priority or security specific improvements weren't seen as important?
In the extremely early days of a startup one doesn't have much optionality. With only three people at the company it really did not make any sense to hire a full time SRE for a pre PMF startup. I'm glad we made those trade offs back in 2011-2012 so that Firebase could be here today to be backed by a dedicated Google SRE team.
Thank you! Are there other examples of new improvements to the development process you've come across? Currently we're positioning Gold Fig to live alongside source control and IaaS. However, we feel there's a huge opportunity to bring the same level of rigor that "version control" encodes to all the (traditionally) non-technical SaaS, enrich existing process (e.g. Gold Fig's log can add more color to your PagerDuty alerts), etc.
Thank you! We are definitely looking at what else is happening in the space with companies like Pachyderm (https://pachyderm.io/) and DVC (https://dvc.org/features). We're also starting to see the development model starting to make its way in to more and more consumer apps as well (Think "document history" in things like Google Docs). Our view is that as more and more of these services specialize the analogous "Version Control for X" is inevitable.
Agreed that the surface area around the out-of-band changes is a concern. We find that educating our users around getting the extension installed team wide is the primary approach by way of policy (in GSuite orgs, you can install extensions team wide) or training (on-boarding docs/new hire orientation). Just as with source control we can commit straight to the main branch, it's through policy/training that we do things like mandatory pull-requests/reviews to not "allow" that. Long term we envision Gold Fig plugging in to your projects as a read-only member to pick up any other out-of-band changes.
I have many fond memories of Print Shop! I remember that program would also print "greeting cards" that you'd fold in quarters. The banners were a pre-birthday task that'd never get overlooked :)
It's interesting that an entire category of features fell by the wayside as a byprodct of the elimination of form-feed/perforated paper.