Things don't change much on old Java Street. Used to be the place to be. These days you'd be lucky to see a new face.

/example

@hube Zenhub is a plugin for github. The issues would exist without it.

@Tobix Looks brand new. Quick find

Have the same keyboard!

First write the test, then solve the problem. TDD in a nutshell.

Recognising the coffee is bad is the first step towards improving

🍀

Computerphile is pretty good.

https://m.youtube.com/user/...

Hopefully it's not the real code and alerts security that someone is trying to break in.

@by2coffee oh interesting

F+1 for help!

Commented out code, unformatted code, untested code etc.

Well worth reading up on her. Pioneer in the world of software engineering.

https://en.m.wikipedia.org/wiki/...

Maintaining an old Java framework
‎(ﾉಥ益ಥ）ﾉ ┻━┻

You want to get something working as quickly as possible so you don't get bored or someone does the same thing. If it takes off you can always rewrite it. Twitter was originally written in Ruby on Rails but it's back end was rewritten in Scala among others.

I forgot the quotes @linuxxx

But it's for our own good :)

The image is from 2007. Maybe we have moved on.

Meta meme

sudo make me a sandwich joke

Both have great blogs well worth a read.
joelonsoftware.com
codinghorror.com

Seen this in a test lately.

var foo = 'bar'
var bar = 'foo'

What about margins?

The answer is No if you don't ask.

Build a formatter into your commit process.

Comments should be reserved for edge cases when it's not obvious why something is being done.

It should not explain what the code is doing but why it is doing it.

Standard scenario with TDD

Bring this up at the next review. It's a meeting cost calculator. It's the only thing management understand.
https://hbr.org/resources/html/...