This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-01-14
Channels
- # adventofcode (2)
- # announcements (61)
- # babashka (26)
- # beginners (125)
- # calva (63)
- # cider (33)
- # clj-kondo (40)
- # cljs-dev (24)
- # clojure (165)
- # clojure-australia (8)
- # clojure-dev (4)
- # clojure-europe (44)
- # clojure-finland (1)
- # clojure-greece (4)
- # clojure-losangeles (1)
- # clojure-nl (28)
- # clojure-taiwan (3)
- # clojure-uk (64)
- # clojurescript (2)
- # core-async (14)
- # datomic (34)
- # docker (2)
- # fulcro (9)
- # garden (1)
- # jobs (4)
- # jobs-discuss (21)
- # kaocha (3)
- # off-topic (48)
- # pathom (4)
- # practicalli (3)
- # remote-jobs (3)
- # shadow-cljs (46)
- # spacemacs (6)
- # sql (4)
- # tools-deps (22)
- # xtdb (5)
- # yada (2)
Morgen, maybe finally going to ‘production’ today. With a project they started on 3 years ago..
Might take some time longer.. very happy that I’m just along the last half year for this project and not from start.
I remember someone giving a talk a while back and told the story about his job having yearly release cycles. But once they released they had to do a lot of bug fixes. To prevent this issue, management thought of the idea to have a two year release cycle instead of one. The speaker suggested to them that maybe it would be better to release faster. At which point he almost lost his job
Huh.. Unless it's avionics software or something very very mission critical.. That doesn't make much sense.
not sure I agree... the problem here is that they wrote lots of code, never tested it properly and then tried to do a big bang update. For mission critical (Avionics) software you would do loads more testing and do things like proofs etc. very different process.
but it reminded me of story from one of my previous employers.... they released the onPrem version first and then tried to upgrade the cloud... and this failed... so they reverted to the old version... and then the execs demanded new functionality before attempting to upgrade again.
Yes, I also like libraries that first put the code in production, before making a release. Lacinia does this.
@U052852ES Can you explain that Thomas, since I don't understand what the advantage would have been of 'cloud first'? What if that scenario went wrong: upgrade the cloud: OK, but releasing onPrem: fail?
with a onPrem solution that is not really possible as companies only want to upgrade once is a while. (not automated downloads of new packages as your Linux distro for instance)
does that make sense @UFLE01UV8?
Ah, OK. But there's not a (big) problem then of functionality being out-of-sync (one colleague using onPrem version 1.x, other colleague using cloud version 1.x+n)?