This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-02-23
Channels
- # aws-lambda (1)
- # beginners (11)
- # boot (456)
- # cider (3)
- # cljsrn (7)
- # clojure (340)
- # clojure-berlin (6)
- # clojure-dev (207)
- # clojure-germany (12)
- # clojure-greece (3)
- # clojure-italy (3)
- # clojure-russia (12)
- # clojure-spec (42)
- # clojure-uk (29)
- # clojured (7)
- # clojurescript (125)
- # datascript (1)
- # datomic (47)
- # defnpodcast (4)
- # emacs (30)
- # events (7)
- # hoplon (13)
- # instaparse (64)
- # jobs (13)
- # jobs-discuss (1)
- # lein-figwheel (1)
- # leiningen (10)
- # luminus (1)
- # lumo (14)
- # off-topic (10)
- # om (16)
- # om-next (3)
- # onyx (1)
- # pedestal (3)
- # protorepl (5)
- # re-frame (17)
- # reagent (66)
- # ring (1)
- # ring-swagger (13)
- # spacemacs (12)
- # specter (4)
- # untangled (272)
- # vim (4)
- # yada (24)
has anyone tested out http://tynan.com/cruisework ?
My experience is that all jobs have crunch time, the real differentiation is how often it happens.
I know that I am very lucky at my job. I had 2 crunch times in 5 years. Where crunch time = working 6 hours longer on friday once and get one day free a few weeks later.
I feel like most of the jobs I’ve had have been so poor at managing times that 70% of the time there’s not much work to be done then 30% it’s a mad scramble to finish.
7h3kk1d : That's true for anywhere you work, really. Even outside of software. It comes from procrastination, whether that be your team, or your clients.
@jstew thanks, I was just hoping I got unlucky and would eventually find a place that operated differently.