Habits of Efficient Developers 

Conclusion he made in the slides: 1. Focus a. disable notifications b. pair program c. rest d. one thing at a time 2. Master your IDE a. Functionality b. Shortcuts c. Pair Program 3. No menial work a. Write programs b. Avoid GUIs c. Automate testing d. repeatable dev env - Docker 4. Fast Feedback a. TDD b. REPL c. Pair program

Just dont write any bugs, you end up saving so much time that way

Great talk. The notification is very important and I have listened to this talk many times just for it. It's my greatest flaw and I am trying to cure it. Thank you for this.

1. Disable all notifications.... Employer: *ARE YOU NOT GETTING MY EMAILS?*

Awesome tips and tricks. Really helpful. Thanks for sharing your experienced knowledge.

Great summery! Deserves so much more devs to see that and implement!

Pair programming is basically finding someone who knows more than you and letting them teach you

jq can do much more than pretty-print. It can run queries on the JSON to extract fields and much more. No more grepping or cutting to extract fields. :)

9:48 I didn't know code could be written on the command line in Bash. I learned something.

33:30 that notification at the end was golden 😁

jq is not only for formatting but also for extracting values from json

What he's also talking about is self-discipline. Art or a practice of any kind is a discipline, treat it like karate practice.

13:27 yea of course everybody can do it. Definitely! [EDIT] 13:50 "What did I get wrong?"

What if when you are learning a script language, u search documentation, it's not complete, even forum is not complete, then you have to trial and error, is there a more efficient way to go around this... I felt like doctors don't have this issue as what they learn is accumulate, whereas as programmers u may find the solution to an issue, but have forgotten the solution when u meet with the same issue and it take u hours to solve, as if you have not solve the issue before, a fair amount of time it feels like the knowledge in IT is very not memorable, as most solution is reference from Google search hence won't have the memory of past solutions, even when you have solve it several times... Not touching the knowledge for years can make u forget about it... And it's so frustrating coz I bet doctors remember about their jobscope

15:03 I whole heartedly disagree. UIs can speed you up A LOT! That's why IDEs exist. Otherwise we could all code with vim and everybody would be happy. E.g. take IntelliJs git integration: when I want to rebase my branch onto main: UI: 1. I click the "fetch all" button 2. in the git history UI I right click on "origin/main" and in the up coming context menu I click "rebase 'my-branch' onto 'origin/main'" 3. I now can resolve merge conflicts via the 3-way-merge UI including the incredible helpful "resolve automatically" button in IntelliJ! terminal: 1. I type in "git fetch" 2. I type in "git rebase origin/main" 3. I now have to manually and awkwardly go through the code in my terminal and resolve everything step by step First way is much much faster objectively.

VIM OR IDE? I mind that lady for skipping that question☹ Didn't he say we shouldn't use GUI? Unless if we are working with Java Platform😬

Visual Studio telling us there are some updates... :)

VIM vs IDE deserved to be answered.

these are some useful points

Great talk. :)

couldn't be more right about avoiding guis... i see almost no point to soapui or postman, or all the sql database or cloud uis. The only benefit I see is that it offers some discoverability of the options which might be more efficient than reading the documentation. However, the tool should always tell you what underlying shell/curl/sql command it issues for you so that you can copy and automate it.

Awesome tips

Could someone explain the REPL part? Is it something integrated into IDE or what? I've found the repl.io service, is that the same thing?

Hi excellent talk :) Can I make a video with some of your slides on my channel ? thanks !

why was vim/ ide the question ignored? :O

Oh man, the only thing worse than having no tests, it is to have tests that confirm the WRONG behavior.

my distraction is twitter... it actually stresses me up.

jq can already do what he did with grep... but eh maybe the skill to do it with grep is more transferable...

Conclusion 33:02

Solomon missed Vim / Even it was in questions..

for i *in* `cat...

God bleass you

I don't agree on dont use GUI. It's way faster to rebranch, pull, push etc on a GUI than writing that typing that yourself.. It's all about what's faster and if the GUI is faster then that is better, fact.

dafaq ? O.o ? 13:38 , its so easy lol

I did not agree with switching things off, as a developer is not about coding. But thanks for sharing your thoughts.

25::04 clojure FTW

as expected, under-reted

Imagine this dodgy malaka being your manager...

this is way to fast spoken for me.

What is this recent fashion of putting a word definition on screen and repeating it. We're not morons. That's how I know a talk is bloated.

Well that was pointless.