3 ms·
> our pilot use case driving our eng priorities – an internal support app for a Series B SAAS startup While your passion for the project and excitement at its
by jungturk 4y ago
> our pilot use case driving our eng priorities – an internal support app for a Series B SAAS startup
While your passion for the project and excitement at its prospects are clear (and I've very much enjoyed following along), this comment makes it sound you've opened a yak barbershop inside this poor support department.
- jameshart 4y agoWanted a vanilla zendesk implementation; got a new UI development paradigm.
- arinlen 4y ago> While your passion for the project and excitement at its prospects are clear (and I've very much enjoyed following along), this comment makes it sound you've opened a yak barbershop inside this poor support department. Perhaps something useful comes out of it. If I recall correctly, CMake (the de-facto standard build system for C++ applications) originated as a yak shaving subproject of a medical visualization application.
- dustingetz 4y agothey are excited by our “lowcode for CRUD apps” RAD tool whose next-gen I/O requirements are the reason we made Photon- “minimum level of ambition that is useful” - see http://www.hyperfiddle.net http://www.hyperfiddle.net
- jungturk 4y agoI'm happy to hear you're in a battlefield environment that's supportive of the additional opportunity, and I'm excited to see what pops out next.
- mananaysiempre 4y agoI hear the Facebook people once tried to make the unread notification counter stop getting stuck, and React came out :) In all seriousness, though, if people are constantly trying to shave the same place on the yak (like web frontend state) ... Maybe there’s just a concentration of unsolved suckage there?
- kennytilton 4y agoWorse, I am pretty sure. That counter is what spawned the Flux architecture. Because React had no solution, mind you.