Fork me on GitHub

good morning!


anyone finding their local/national gov'ts are increasing funding for cycling/walking/active travel? Just responding to 2 things locally in Scotland


what do you mean by “funding”?


as in money being spent from gov't budgets to do things like put in new bike lanes, signs, etc


in germany we get a tax-decrease for commute distance to the work


ah, hm, good question


so infrastructure spending


(tho sometimes infrastructure is just "magic paint that is meant to protect cyclists from cars")


😄 I feel infrastructure for cyclists in munich is okay’ish… they could however improve big intersections


so that you don’t get ran over by cars or trucks so easily


they put in a whole bunch of "temporary" extra bike lanes in Berlin. Of course some of them are just used as extra parking space... Really hoping some of them become permanent.


can someone explain to me why I dislike (for in clojure so much?


there are reasons for that...


maybe because it looks like an imperative construct?


I don't find too many times where it couldn't just be a map


and I’m having fun with gradle dependencies…  (not clojure related though)


I suppose for is good for cartesian products, but tbh, I just reach for math.combinatorics then so I can be explicit


I use doseqquite a lot.


(where people typically (doall (map f seq))


I've started using run! rather than doall

Ben Hammond13:05:34

its a false friend, that's why

Ben Hammond13:05:54

well, perhaps not if you have a python background

Ben Hammond13:05:15

but from a java perspective its squarely in the uncanny valley

Ben Hammond13:05:53

plus it doesn't compose...

❤️ 4

hey how do you guys forster good code quality in your team? do you do training? workshops? do code reviews suffice?

Ben Hammond14:05:43

code reviews, of your own as well as other people's

Ben Hammond14:05:40

but I find it can take a while for 'good quality' to emerge; good quality code is code that can be easily adapted to changing businesss requirements

💯 4
Ben Hammond14:05:24

which is a bit chicken-and-egg it takes a while to figure out what the business is likely to want to change and what they are not

Ben Hammond14:05:49

that was always my experience anyway

Ben Hammond14:05:47

If you write something, and it works, and it doesn't need to be touched for the next 5 years, then abstract notions of quality are less important


I’m really frustrated by our team, the guys have no urge to improve the quality. just keep adding more and more mud, just to have instant gratification and move to the next ticket


I think I’ll need to set up some workshops, which is again another problem for me because it costs a lot of my time

Ben Hammond14:05:13

well, if you are getting paid by the ticket

Ben Hammond14:05:20

then that is your incentive

Ben Hammond14:05:23

once of the downsides of weakly types languages is that people get a bit frightened of changing anything


no, there’s no such policy


ah I’m not even talking about clojure; we do kotlin. But my question would also apply to Clojure of course

Ben Hammond14:05:52

you need really strong generative testing to overcome The Fear

Ben Hammond14:05:17

clojure has the 'additive' philosophy to change, which sometimes gets (mis) interpreted as > we are not allowed to change anything that has been written


maybe individual code reviews is not so bad and we should do reviews in groups in front of a projector

Ben Hammond14:05:29

which seems very unfortunate


interesting, didn’t know 🙂

Ben Hammond14:05:17

I don't think it is supposed to mean that but that might just be me


clojure is for me yet another thing; since we’re not a clojure shop I mostly try to sneak in some clojure as side projects into the work 😄


learning good practice there is even more difficult to me