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
Very good video! Thanks a lot! Some useful lessons learned: > Minimize interruptions: Disable all notifications. ✅ Use headphones to pretend you are unavailable for interruptions. 😀 Practice pair programming: one person can stand up to handle interruptions while the other stays focused on coding. 😮 > Focus on one thing at a time: avoid context switching by completing one task before moving on to the next. ✅ > Master your IDE: Learn the functionality and shortcuts of your IDE. 👍👍👍 Consider pair programming to learn from other developers. 👍👍👍 > Automate manual tasks whenever possible. 👍 > Write clean code: 👍👍👍👍 Avoid graphical user interfaces (GUIs) for complex tasks. 🤔 Write unit tests: write a failing test first, then write code to make the test pass. This helps catch bugs early on. 👍👍 > Use a REPL (Read-Eval-Print Loop) to experiment with new libraries or code. 🤔 > Reflect on how you are working and continuously learn new things. 👍👍👍
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.
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. :)
eMails are read three times a day: Before you start work; when you start your main break before leaving the desk; after you finished the work for the day. If it is so urgent that it can't wait for one of those three points in time, my employer can feel free to come to my desk and telk to me directly.
ok, and? There is always someone "who knows more than you", and no one lives forever. If you as a senior Dev dont plan to sit on your ass until you die at your workplace, passing the knowledge is probably good idea dont you think?
some people don't understand this, most people think pair programming is contributing equally to solving a problem. I understand you shouldn't just sit and not code/think but ask questions about certain things Following up on those questions is what pair programming is. Being Taught by another person.
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.
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
Haha, this is why you should pair-program often. If he had someone else with him, they would have figured it out together in an instant... or at least, faster than usual.
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.
Repl is the interactive environment that many languages offer. Bash terminal is a kind of REPL (read evaluate print loop) since you can run command line code like he shows. But you would get the same with nodejs by typing node (or the console in the browser), or even python (once installed just type python and there you are!). Hope this is helpful although quite late :-)
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.
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
Thanks you saved me 37+ minutes
Thank you sir for saving my time
I think you forgot "timebox tasks" 14:20
I screenshot it, thanks for the summary!
Merci pour le résumé!!!
Very good video! Thanks a lot!
Some useful lessons learned:
> Minimize interruptions:
Disable all notifications. ✅
Use headphones to pretend you are unavailable for interruptions. 😀
Practice pair programming: one person can stand up to handle interruptions while the other stays focused on coding. 😮
> Focus on one thing at a time: avoid context switching by completing one task before moving on to the next. ✅
> Master your IDE:
Learn the functionality and shortcuts of your IDE. 👍👍👍
Consider pair programming to learn from other developers. 👍👍👍
> Automate manual tasks whenever possible. 👍
> Write clean code: 👍👍👍👍
Avoid graphical user interfaces (GUIs) for complex tasks. 🤔
Write unit tests: write a failing test first, then write code to make the test pass. This helps catch bugs early on. 👍👍
> Use a REPL (Read-Eval-Print Loop) to experiment with new libraries or code. 🤔
> Reflect on how you are working and continuously learn new things. 👍👍👍
Just dont write any bugs, you end up saving so much time that way
That's impossible for us you know buddy
Just don’t write any code. Saves you from bugs, writing code, and probably having to show up to work. Win/win lol.
Or fail fast, so you know what's wrong on the system.
@@unfriendly3255 It is a joke you know
It’s obviously a joke guys
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.
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. :)
Thank you
1. Disable all notifications....
Employer: *ARE YOU NOT GETTING MY EMAILS?*
:D
hahaha
eMails are read three times a day: Before you start work; when you start your main break before leaving the desk; after you finished the work for the day. If it is so urgent that it can't wait for one of those three points in time, my employer can feel free to come to my desk and telk to me directly.
Pair programming is basically finding someone who knows more than you and letting them teach you
ok, and? There is always someone "who knows more than you", and no one lives forever. If you as a senior Dev dont plan to sit on your ass until you die at your workplace, passing the knowledge is probably good idea dont you think?
@@ezracramer1370 lmao u must be fun at parties
@@xXZian6Xx agreed but, i mean, he's not wrong..
some people don't understand this, most people think pair programming is contributing equally to solving a problem. I understand you shouldn't just sit and not code/think but ask questions about certain things Following up on those questions is what pair programming is. Being Taught by another person.
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.
it also means not using a mouse to click a button rather than shortcuts
If you learn vim you'll be faster than anyone that uses VSCode, that's a fact.
doesn't everybody code in vim? Oh!
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.
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
13:27 yea of course everybody can do it. Definitely!
[EDIT] 13:50 "What did I get wrong?"
yeah lol , it bounced off my head . --_____--!
Haha, this is why you should pair-program often. If he had someone else with him, they would have figured it out together in an instant... or at least, faster than usual.
9:48 I didn't know code could be written on the command line in Bash. I learned something.
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😬
Great summery!
Deserves so much more devs to see that and implement!
Awesome tips and tricks. Really helpful. Thanks for sharing your experienced knowledge.
Visual Studio telling us there are some updates... :)
VIM vs IDE deserved to be answered.
why was vim/ ide the question ignored? :O
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.
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?
Sorry for the late reply, but i don't know
@@King-bx4ch 😂😂😂😂
Repl is the interactive environment that many languages offer. Bash terminal is a kind of REPL (read evaluate print loop) since you can run command line code like he shows. But you would get the same with nodejs by typing node (or the console in the browser), or even python (once installed just type python and there you are!). Hope this is helpful although quite late :-)
Conclusion 33:02
Oh man, the only thing worse than having no tests, it is to have tests that confirm the WRONG behavior.
Hi excellent talk :)
Can I make a video with some of your slides on my channel ?
thanks !
these are some useful points
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...
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.
a graphic interface faster than the command line? Then you don't know what you are doing, take time to ppractice and learn the command line
Solomon missed Vim / Even it was in questions..
Awesome tips
Great talk. :)
for i *in* `cat...
I'e never made a for loop in bash and I thought that "for i" looked weird, what did he wrong exactly if you could explain?
@@arsacode6145no "in"
dafaq ? O.o ? 13:38 , its so easy lol
Imagine this dodgy malaka being your manager...
I did not agree with switching things off, as a developer is not about coding. But thanks for sharing your thoughts.
This will distract you if you trying to do multiple tasks at the same time
God bleass you
as expected, under-reted
25::04 clojure FTW
this is way to fast spoken for me.
Well that was pointless.
Seek wisdom