HN user

semperos

42 karma

[ my public key: https://keybase.io/semperos; my proof: https://keybase.io/semperos/sigs/RKng60r1yAufwBbFgZKjCjFivrlEuhGUdk6iZiY8vN0 ]

Posts3
Comments4
View on HN

I help build Shortcut (https://www.shortcut.com/) and I think it fits the bill of light—but not spartan—on customization and day-to-day management.

To set up a new Shortcut workspace:

1. Sign up 2. Invite teammates, group them into teams if desired 3. Activate the GitHub/Gitlab/Bitbucket integration, so as engineers work via VCS their work in Shortcut progresses automatically 4. Set your workspace's timezone 5. Turn on/off Iterations (sprints) based on your process. Unfinished stories can be set to automatically roll from one iteration to the next. 6. Turn on/off point estimation based on your process

Then start writing Stories (tickets/issues) to track work.

Going further: Stories can be grouped into Epics. Epics can be grouped into Objectives (with associated Key Results if that's your thing). You can put Epics on a Roadmap to "share out" what your team is planning to work on. All optional, based on how you work and the size of your org.

ClojureScript 15 years ago

To better understand how different ClojureScript is from CoffeeScript, read the last paragraph on the ClojureScript wiki's Rationale page: https://github.com/clojure/clojurescript/wiki/Rationale

It's purpose is not to compile down to vanilla, readable JavaScript, but rather to make it easy to write production-ready JavaScript applications that can easily leverage the "advanced mode" of the Google Closure compiler.