This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-03-19
Channels
- # arachne (1)
- # beginners (108)
- # boot (50)
- # cljs-dev (7)
- # clojure (76)
- # clojure-ireland (1)
- # clojure-romania (1)
- # clojure-russia (7)
- # clojure-spec (33)
- # clojure-taiwan (1)
- # clojure-uk (36)
- # clojurescript (46)
- # core-async (13)
- # datomic (146)
- # defnpodcast (1)
- # editors (1)
- # garden (2)
- # hoplon (1)
- # jobs (1)
- # lumo (7)
- # off-topic (21)
- # om (9)
- # pedestal (1)
- # re-frame (25)
- # reagent (5)
- # specter (2)
- # testing (3)
- # unrepl (3)
- # untangled (9)
- # vim (1)
Morning Jade
Spent yesterday writing C. So that was interesting. Today I'm refactoring & upgrading my completion integration for vim. Quite enjoying it.
@gjnoonan This was mostly mathematics 😮. Generating histograms for 1e9 over large scales.
@gjnoonan weekends going well so far. Just tweaking the talk I'm giving to CS undergrads at Sunderland Uni tomorrow. I'm also leading a TDD workshop after the talk. However, as they do their project work in C# I've got to remind myself of enough to get through it. Although dotnetcore is interesting. Might make me look at F# again.
Same talk as I gave this time last year about Developer Disciplines that I look for in a professional developer...i.e. use of version control, code formating, continual improvement and learning, TDD (used appropriately), testing in general, etc.
Stuff they don't really emphasise in courses
Want to give a quote for the last few slides?
@agile_geek "There are two ways of constructing a software design. One way is to make it so simple that there are obviously no deficiencies. And the other way is to make it so complicated that there are no obvious deficiencies." - C.A.R. Hoare
"Always code as if the guy who ends up maintaining your code will be a violent psychopath who knows where you live." - Martin Golding
@yogidevbear I should have clarified. I want a quote from you not someone else and it needs to be about developer practices and disciplines you think are important. For example "frequent commits to source control", "learn your shortcut keys", "code as if you are going to support your own code...because you might have to.".. etc.
With you
It's what you consider important. Something you wish someone told you before you became a professional
"Write your failing test before the code that is meant to pass it" - yogidevbear
things you never really do at uni: ship code to production, maintain existing code someone else wrote
> Never let anyone tell you that streamlining your workflow bycustomising your editor of choice is yak-shaving and pointless.
do not confuse 'unfamiliar' with 'pointless' (or 'insane' &c)