This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-09-07
Channels
- # 100-days-of-code (1)
- # announcements (10)
- # aws (2)
- # beginners (134)
- # calva (25)
- # cider (29)
- # cljs-dev (43)
- # clojure (130)
- # clojure-dusseldorf (3)
- # clojure-italy (27)
- # clojure-nl (48)
- # clojure-spec (32)
- # clojure-uk (63)
- # clojurescript (75)
- # core-logic (5)
- # cursive (18)
- # datascript (2)
- # datomic (37)
- # emacs (5)
- # figwheel (13)
- # figwheel-main (55)
- # graphql (1)
- # java (7)
- # jobs (11)
- # jobs-discuss (19)
- # juxt (1)
- # leiningen (16)
- # luminus (10)
- # mount (3)
- # off-topic (40)
- # om (1)
- # onyx (1)
- # pedestal (7)
- # re-frame (40)
- # reagent (81)
- # ring (2)
- # shadow-cljs (32)
- # spacemacs (5)
- # testing (1)
- # tools-deps (48)
Fixing migrations troubles, one collection is used in multiple migrations, running at the same time, on mongo..
still trying to fix my react problem. yesterday I thought I had found the problem.. looks like I found a different problem
morning. thinking about development / software lifecycle methodologies.
looks interesting
me neither, but the book touches on a few points that tend to be overlooked/ignored by pure-Scrum methods
as far as I can tell it’s a framework for getting agile in a larger context of “enterprise”; so more focus on delivery and business processes (stuff around development).
of course, some agile evangelists would tell you make your whole org do scrum…
@thomas you worked at IBM right?
some agile evangelists would tell you the whole idea of agile is lost in processes nowadays... 🙂
yeah. what kind of methodology did you typically use for development/project management?
which isn't really surprising as IBM is a very big company, and there are many different parts that don't communicate with each other.
> Our challenge at the moment isn't making agile a thing that people want to do, it's dealing with what I call faux-agile: agile that's just the name, but none of the practices and values in place. Ron Jeffries often refers to it as "Dark Agile", or specifically "Dark Scrum". This is actually even worse than just pretending to do agile, it's actively using the name "agile" against the basic principles of what we were trying to do
At this point 80% of "agile" is people telling others to use Jira - just like RUP in "good old days"
Or maybe I've become too old - so my cynicism has peaked :P
I only heard about RUP on university but not in real life (luckily I guess, I already hated it at uni)
appears to me most of "agile" is actually "scrum" nowadays, used by managers to make development teams ship code frequently and get a sense of control through process over what they're doing
regularly verifying if software development and client requirements still match. whatever you want to call it.
I read this book a few months ago which I really liked -> https://leanpub.com/actionableagilemetrics
at IBM it was decided that RUP wasn't good enough... so they modified it and it became iRUP
It’s basically a way to measure instead of estimate.
I would like to work at a CMM level 5 organisation sometime.. just to see what it is like.
In my experience most estimation techniques don’t really predict the actual time it takes to make the software all that accurately. I’m looking at you planning poker.
Be warned though, I tried the above no estimation thing. It will give you realistic numbers but those are pretty hard to accept for some people.
Yes, and the more experience with the software and organisation the better the estimate, but still there can be surprises both ways.
I keep typing ‘:’ in front of the keys instead of after it querying mongo, and don’t even done any clojure lately
I once wrote some python like this: (func-name arg-1 arg-2)
and couldn't work out why it didn't work (and the editor I was using didn't indicate it was a problem)