https://github.com/Internal-Tools-Hub/CorpHome/blob/master/R...
1,229 karma · joined March 21, 2011
Former: VPEng/CTO @ Caris Life Sciences & Misc Startups
|X: @masonhensley | https://www.masonhensley.com/ | me@{{username}}.com | Vanderbilt Engineering Grad. | Richmond, VA
[ my public key: https://keybase.io/masonhensley; my proof: https://keybase.io/masonhensley/sigs/i7JrDHrUHja1PHcFqVJwLUBt0ET_h3lNJH_c5gN9j0Y ]
https://github.com/Internal-Tools-Hub/CorpHome/blob/master/R...
I'm also happy to walk you (or others in the thread if time permits) though the source code of a closed source app I have over a video call if you need to grok the mechanics/db structure. (email in profile.)
It's got:
- multi-tenancy
- roles with-in each tenant
- sub-tenants (think engineering team vs accounting team vs hr team)
- accounts can be members of multiple tenants
- billing for each tenant (even sub tenants or inherit from root tenant)
- Super Admin & "Staff" roles
- Auditing
If anyone's interested in the open source app, follow here - https://twitter.com/tools_hub
For instance, was there something a particular BA/PM did when they wrote up specs that made your life easier?
There's a spectrum of a Jira issue with a title "User Avatar Upload" and a blank description or even receiving the equivalent length of War & Peace that's confusing and contradicts itself. Thoughts on the middle ground below?
----
Title: User Avatar Upload
Story:
As an Accountant
I want to upload a photo as an avatar
So That other users can quickly recognize my content and contributions.
--
Acceptance Criteria:
1. Should accept .png, .jpeg, .jpg, .tiff file formats.
2. Should reject with friendly notification files that do not match whitelist.
3. Should make copies of image in resized formats.
4. Should store them in storage bucket or CDN for performant retrieval by the users and application.
5. Should not allow execute code to be injected. (Example: malicious JS, PDF, misnamed file types, etc)
Good idea to show the travis example for anyone thinking of migration.
My email in profile if you’d like to check it out.
Clubhouse.io, Asana & PivotalTracker are nice, but a little opinionated (can be a good or bad thing depending on who you are :) ).
I think where Jira really rubs people the wrong way is it's speed, particularly after someone customized it with a byzantine workflow or with dozens of views/reports and no primary source of truth for the team to use. Imagine a PM looking at one report and the dev's thinking another is "the one." A fresh Jira (Cloud verion on corp-name.atlassian.net) with out of the box Kanban board should work for most.
There are some industry vertical plays out there that focus on Agency or Freelancing work.
There are definitely healthy businesses in different market sectors that have popped up to do DataA <=> DataB
I'm oversimplifying it... there is so much more supply than demand that groups that can't take physical delivery of a contract (no space) and are paying to have it taken off their hands.
Better discussion here: https://news.ycombinator.com/item?id=22924321
Over the last few years, I’ve found myself in deja vu moments coaching Subject Matter Experts (SME’s), Product Managers, developers on their user stories & requirements for normal stuff we see in most software applications... Think user management, forgotten password flows, csv uploads, common customer service tasks etc - mostly solved problems from both an Engineering & UX perspective. The problem is that teams keep reinventing the wheel on these basics at the product level before code is written. It frustrates product teams as meetings and product debt build up and users end up taking their share of the pain. So I went down the rabbit hole and analyzed ~200 well built products, gathered “all the things” (about 800 “Story Specs” + Acceptance Criteria) & created a tool for importing them into project management tools.
Thesis: 60-80% of the software built by most teams is a solved problem. If we can better automate the definition of the basics earlier in the life-cycle via a common vernacular, there will be more bandwidth for smart people to do smart things. (I’ve got a blog post brewing about Maslow’s hierarchy of product needs & how innovation/ smart people get dragged down.)
Here’s a quick video of the tool (same video, loom & youtube depending on your preference):
- https://youtu.be/6jGBVN_ab_U
- https://www.loom.com/share/9afd3225b0e3418da802278f2bea9e33
Some Screenshots (via rough docs): https://docs.hipspec.com/docs/workflows/story-spec-pushing/
Free tier has some random user stories & will be further built out with listings to help get Open Source Projects into team backlogs… tangent for another time. Registration Link: https://app.hipspec.com/users/sign_up
Random thanks to @jason, @mijustin, @jonbuda, @derrickreimer, @r00k, @robwalling & @GrantM for their podcasts that have given me consistent company while working on this. And Startup School, what a blast. Thanks for checking out HipSpec.com, I'm around for feedback & chit chat.
TLDR: I identified ~800 user story primitives + associated acceptance criteria that are relevant to most software product teams & made them easy to import into backlogs.
https://www.barrons.com/amp/articles/softbank-may-get-out-of...
Desk: https://www.homedepot.com/p/Husky-62-in-Adjustable-Height-Wo...
Overhead TV - don't really use it, tried to add some stripe info + magic mirror via raspberry pi... please don't tell my wife I admit to it not being useful.
Picture from January - https://storage.googleapis.com/hipspec-marketing-images-publ...
Also, not a lawyer, but I believe there is a minimum wage thing in California. I think It's mentioned in this startup School lesson (~9 minutes in):
- Video: https://www.youtube.com/watch?v=LBC16jhiwak&feature=emb_titl... - Transcript: https://jotengine.com/transcriptions/NDLakO9K0GVmyY6d8B1uAQ
Some companies build it into their systems to automatically catch and mask that data, sometimes someone has to rollup their sleeves and do it manually.
I'd wager that 95%+ of orgs have tons of sensitive customer data scattered into chat messages in Slack, Teams, Hangouts, etc that would horrify most of us here.
Check out this: - https://cloud.google.com/dlp - https://www.youtube.com/watch?v=MY3PjFpI3rE
I’ve been in situations where outsiders, clients or stakeholders want to know there is one... but don’t necessarily care about the content. Eek.
What’s the saying? Everyone has a plan until they get punched in the face?
The supply chain issues alone are going to be a big hurdle for traditional PPE delivery to those that need it.
While efforts like this of course can't compete with the volume of a full on manufacturing plant, they will probably help the tail of smaller provider groups that can't tap into the supply chain.
Elective procedures are postponed indefinitely. Procedures contribute a hefty chunk of revenue in healthcare.
I’d be careful being absolutist with that comment. The cash flow of many hospitals is going to get strained at the very least in the near future if they aren’t billing for a large chunk of their services.
https://github.com/rudderlabs/rudder-server/pull/183
Cool project!
- https://www.wildflower.org/project/ecological-roadsides
- https://www.wildflower.org/plants-main
- https://texashighways.com/culture/people/a-runner-reflects-o...
They had an image in the repo, but it wasn't referenced in the readme.
Here's a rough survey, should be able to see result graphs afterward submission:
https://docs.google.com/forms/d/e/1FAIpQLSfUkV2P1VxAnRSD88eU...
Raw data results link for community to look at: https://docs.google.com/spreadsheets/d/1x59q4CbEGOeYirskJ7Ac...
===
Main Q: ~16 hrs/week (had about 10 1:1's/week for a while)
Bonus Q: 2hrs
I'm not advocating a sterile one size fits all grey dystopian outfit equivalent for everyone. But when you look at the landscape of software, I'd argue that teams forget what the equivalent concepts of what pockets or zippers are.
Similar to how many orgs will spend $100k's to have a half baked mobile app when a web app or off the shelf CMS would not only suffice but be a better solution for the end users's needs.
Point being - get the basics right, leverage the immense value that's been provided by the open source community and then & only then do you start redecorating.