HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
Nax
longflow-manifesto
OPEN SOURCE2016–2017
Nax / longflow-manifesto

longflow-manifesto

:coffee: The longflow manifesto

5Distinct people
5Mentions
0Explicit recommenders
634GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

:coffee: The longflow manifesto

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 5:04:57 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by week5 dated mentions

Observed mentions: 2016-12-15 12:16:39 UTC to 2017-02-02 08:12:12 UTC. Weeks start Monday, UTC.

0122016-12-12 00:00:00 UTC to 2016-12-19 00:00:00 UTC (exclusive): 2 mentions; 2 submissions, 0 commentsDec 122016-12-19 00:00:00 UTC to 2016-12-26 00:00:00 UTC (exclusive): 2 mentions; 1 submissions, 1 comments2016-12-26 00:00:00 UTC to 2017-01-02 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-01-02 00:00:00 UTC to 2017-01-09 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsJan 22017-01-09 00:00:00 UTC to 2017-01-16 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-01-16 00:00:00 UTC to 2017-01-23 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-01-23 00:00:00 UTC to 2017-01-30 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-01-30 00:00:00 UTC to 2017-02-06 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsJan 30

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Dec 122016-12-12 00:00:00 UTC2016-12-19 00:00:00 UTC220
Dec 192016-12-19 00:00:00 UTC2016-12-26 00:00:00 UTC211
Dec 262016-12-26 00:00:00 UTC2017-01-02 00:00:00 UTC000
Jan 22017-01-02 00:00:00 UTC2017-01-09 00:00:00 UTC000
Jan 92017-01-09 00:00:00 UTC2017-01-16 00:00:00 UTC000
Jan 162017-01-16 00:00:00 UTC2017-01-23 00:00:00 UTC000
Jan 232017-01-23 00:00:00 UTC2017-01-30 00:00:00 UTC000
Jan 302017-01-30 00:00:00 UTC2017-02-06 00:00:00 UTC101

What Hacker News says

5 sources
Comware Australia | NodeJS, AWS, DevOps | Melbourne Australia | Permanent, Contract | REMOTE (Australia Only) Looking for a software engineer with extensive experience in nodejs, aws and elasticsearch and knowledge of Ansible, Docker and Kubernetes to help with developing and extending an audience management platform. which currently collects in excess of 100M+ events per day. Front-end experience in VueJs or ReactJS is a bonus but not required as is a fervour for entrepreneurialship. If you have a passion for quality and automation, can hit the ground running and work autonomously then email me directory at jima at comware dot com dot au. The interview process is lightweight, no code review, no testing just point me to your github account or some projects you've worked on and let's grab a coffee, or hook up over skype for a chat. I am a
Read the rest
big fan of the Longflow Manifesto (https://github.com/Nax/longflow-manifesto), collaboration and knowledge sharing. Willing to pay premium for the right person
In Ask HN: Who is hiring? (February 2017)
It's really funny. To say the least. The "Typical Implementation"[1] is EXACTLY how a mature agile team behaves. The only difference is that business decisions are delegated to the PO when the devs DON'T have the whole business knowledge (if they do, then yeah they can make the call by themselves, but that's NOT where most companies stand for!). It's pretty common for a company that is not technology focused on having a PO to decide priority, make the call if a task is unneeded and decide if things engineers learned (called spikes) will change the business priorities and will make you go back to step 1. The difference is that you need communication skills, something most people lack. Source: I am doing consulting for a year in the best tech team of a multi billion dollar Australian company that had a dysfunctional team and now it's crazil
Read the rest
y performant. The team is the least bug producer of the whole company. It's like working from 09:30 to 17:30 with 2 hours interval and still produce astonishing results. Sorry for the ad verecundiam[2]. [1]: https://github.com/Nax/longflow-manifesto/blob/master/README... [2]: https://en.wikipedia.org/wiki/Argument_from_authority
In The Longflow Manifesto

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.