Process Street, a workflow and checklist software company, writes about startups, process management, and small business tools.
HN commenters mostly mention it as a workflow tool when discussing SOPs and repeatable processes; some link it when promoting the company itself.
It's crazy that we're living in the world of (almost) infinitely available information, big data etc. in 2022, but recruiters are still often secretive and shady.
For the general audience, let me drop some advice here that helped me during my job search:
- I knew what I was looking for (remote-friendly tech startups with their own product). I suggest you think this through as well.
- No Linkedin profile! Really, not needed unless want a corporate job. (Though I have a tiny and mostly neglected personal website which is appreciated by most companies.)
- Browse and actively follow dozens of job boards like the one in parent comment. DuckDuckGo is your friend. In a few days or weeks, you'll find out your 'taste' in terms of jobs that interest you and easily filter out mediocre offers.
- Draw boundaries and put your bar high. Know your desired compensation range and ask right away if not indicated. Reject take-home homework, leetcode interviews etc. if you don't like them. The interview process tells a lot about the company culture and you're also getting to know that company, not just the other way.
- Work on your resume! An investment that pays back like wonders. It also makes you much better prepared for interviews. There are some very useful books out there like "The Tech Resume Inside Out". Best $20 I've ever spent.
This way, you have total control in your job search and will have zero awkward HR phone calls. Though I admit that if you're looking for corporate jobs,…
The title is somewhat misleading because only 48/250 had actual pricing pages, the others had what really amounts to "contact us" pages for their sales teams. Fortunately it's still an informative read, and even 48 pages are enough for meaningful discussion of pricing pages. The original post has additional infographics at the end of the article (a helpful way to reason about ideas contained within after going through it all in text): https://www.process.st/2015/12/saas-pricing-pages/
As a consumer I often feel like contact-style "pricing" pages are a way of trapping customers into a hard-sell. Granted some pricing structures are complicated out of necessity, especially those where usage plays a significant role in the cost to the provider (substantial bandwidth transfer, hardware/setup, human resources). More often than not I immediately abandon any such service if contacting for pricing is the only option. It was surprising to see 80%+ (202/250) of companies didn't list their pricing because my personal real-world experience feels like the inverse.
The article discusses the reasons for the contact-only approach, which boil down to preventing biases for enterprise customers. While that's understandable in some situations, not all SaaS is intended to target enterprise customers. It goes on to consider pros/cons of the multifaceted concept that is tiered pricing. If read this much of my comment but not the article, go read it now!
(A couple typos for the author: "boost…
Process Street | https://process.st/ | REMOTE
We believe that the way most teams capture their knowledge today is broken. Knowledge belongs where the action happens – not in documents hidden in a virtual filing cabinet.
Process Street is where teams bring their operational knowledge to life using rich, automated playbooks. Often described as checklists with superpowers, our platform enables you to build, run, and gather insights for all your team's recurring workflows.
We're a data-informed product team using Basecamp's Shape Up methodology. It's a fast-paced and highly empowered team environment where you're given a ton of autonomy to create.
READ MORE about our method and team:
https://www.process.st/shape-up/
https://www.process.st/full-stack-engineer/
APPLY -- https://www.process.st/jobs
---
Engineering
- Sr Engineer, Full Stack
- Lead Engineer, Full Stack
- Staff Engineer, Full Stack
- Principal Engineer, Full Stack
Product
- Lead Product Designer
> I want that temporally and semantically linked set of activities to appear on a timeline with links to and from the various tools I use
Sounds like what you want is a repeatable, digital workflow. Using workflow software like Process Street (https://process.st) you can build that documentation as part of performing the work itself. You could capture, say, the AWS policies you create and the ARNs they’re associated with in the workflow. You could automate integrations with Jira (or just about anything if you use Zapier) as steps are completed. You can start off simple and build on as you go.
Disclaimer: I work for Process Street.
It looks like Microsoft Word at some point had the convention that typing Ctrl-: followed by a vowel got the umlauted vowel:
https://resources.german.lsa.umich.edu/schreiben/umlaute/ https://www.novalutions.de/en/how-to-type-an-umlaut-in-microsoft-word-a-simple-guide/ https://www.process.st/how-to/type-an-umlaut-in-microsoft-word/
and IIRC something similar worked for Ctrl-' + e = é , Ctrl-` + a = à, Ctrl-~ + n = ñ, and so on.
So there's at least some association for (punctuation mark) + (vowel) = marked vowel and I could see people dropping the Control key and doing what's done here.
I ran into this today while searching for a way to merge channels in Slack. A google search turned up this result https://www.process.st/how-to/merge-channels-in-slack/ which describes an in-app method that does not exist.
That entire website should be banned from Google.