This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-05-18
Channels
- # ai (1)
- # beginners (71)
- # boot (15)
- # cider (26)
- # clara (4)
- # cljs-dev (81)
- # cljsrn (26)
- # clojure (393)
- # clojure-berlin (2)
- # clojure-dev (5)
- # clojure-dusseldorf (1)
- # clojure-greece (5)
- # clojure-italy (6)
- # clojure-russia (97)
- # clojure-serbia (11)
- # clojure-sg (2)
- # clojure-spec (14)
- # clojure-uk (66)
- # clojurescript (58)
- # core-async (19)
- # cursive (18)
- # data-science (2)
- # datomic (75)
- # emacs (20)
- # events (5)
- # figwheel (1)
- # graphql (2)
- # hoplon (29)
- # jobs-discuss (3)
- # juxt (6)
- # lein-figwheel (1)
- # london-clojurians (2)
- # lumo (29)
- # mount (9)
- # off-topic (4)
- # om (16)
- # onyx (25)
- # other-languages (2)
- # pedestal (38)
- # protorepl (2)
- # re-frame (20)
- # reagent (9)
- # ring-swagger (6)
- # sql (10)
- # unrepl (3)
- # untangled (19)
- # utah-clojurians (1)
- # videos (2)
- # vim (20)
IPv6 addresses are valid too. Perhaps you should be specific.
My (high recommended) ISP supported IPv6 over a decade ago.
Aye up
@malcolmsparks yes, we support IP6 as well. To us it is just data and Postgres has a type for inet addresses and those are both ip4 and ip6.
@mccraigmccraig you shouldn't be ashamed of doing TDD. It's a tool not a religion, use it when it works for you. It's just that for me that's almost all the time!
when I try to do TDD I tend to write both the test and code at the same time... because when I start most of the time I am not even sure what the end result should be. hence writing the test first is quite difficult.
I tend to write tests after writing the code. I find less value in the 'write a failing test' approach when you have a REPL.
Plus, the continual switching of focus between writing good code and writing good tests is hard for me.
Also, I find I have to write better code first time with Clojure because it is harder to refactor.
That's not necessarily a bad thing though.
I use the REPL to help examine data, then write the tests making assumptions about the API from the client's perspective, then implement, then I usually find my assumptions are not quite right so I refactor test and so on. I think it's whatever works for you but I've caught so many mistakes by having tests first that I'm convinced it works for me.
I find the continually switching from test to implementation is the thing that helps me not make mistakes as I don't just focus on the details of the implementation but keep switching back to what the client of the fn/API wants.
Morning
Re: writing failing tests first... my understanding is that it should provide better code coverage than writing the tests retrospectively, but like Chris says, it's just "a tool not a religion"
@yogidevbear it's not just about code coverage per se. I've practised TDD since 2004 and I just work much better with it than without. Doesn't mean I don't use the REPL a lot as well. My views on TDD are well documented - http://devcycle.co.uk/TDD-Thats-Design-Done/ http://devcycle.co.uk/To-Do-Damage/
Thanks for the links. I'll make a note to read through them a little later 👍
@malcolmsparks could not agree more on the REPL driven dev vs test first point. but why is it harder to refactor?
Steve Yegge’s reasoning on why Kotlin: I'm too blue-collar to use Clojure
http://steve-yegge.blogspot.co.uk/2017/05/why-kotlin-is-better-than-whatever-dumb.html
and maybe it is just me... but sometimes that devalues the next time that person is being an advocate.
I don't think admitting you've changed your opinion devalues the original opinion. I held loads of technical opinions 20 years ago that I've moved from through experience.
I think you just need to justify why.
I think you have said it way better then I ever could @agile_geek 🙂
@glenjamin what are you talking about...I still love COBOL!
I feel as though I am missing something... The only opinion I've felt the need to modify is how much I like PHP... All the other languages I can program in and have done "for money" are pretty much equal in my affections... I mean I tend__ to enjoy Clojure more, but I still get a huge kick out of writing code in Python and Ruby, and even (god forbid) JavaScript... Is it not just a case of "tool for the job" and whatever makes the most commercial and technical sense, and in the end it's all an accommodation? I mean why does anyone care what Steve Yegge used to think and what he thinks now - if you like Clojure and you feel it fits your needs then surely that's all you need?
I mean there are hundreds, nay thousands of people out there using Scala, surely they wouldn't be if they cared about anyone's opinon?
well spoken @maleghast
lol @ It's not "weird" like Clojure or Scala (and let's face it, they're both pretty weird.)
guess i like my weirdlangs
And Scala's not weird either to be fair....but it's not simple
@thomas - I have no clue, I did not even know that there is a language called "APL", though it looks as impenetrable as Befunge...
We were once talking about APL.... and one of the guys asked as what the "A" stood for.... 😉
and I agree @maleghast APL is a write only language. and even that is difficult as you'll a special keyboard.
surely there are some people somewhere who love APL @thomas ?
I am sure there are @mccraigmccraig .. but I suspect people like that just like a lot of pain.
@jonpither - Morning 🙂