Yisrael Dov @yisraeldov@mastodon.technology

RT @martinmthomas@twitter.com
@unclebobmartin@twitter.com I think I will be surprised if a plumber ever tells "Leak has been fixed. You can check it later and call me if it is not fixed". All devs must show similar professionalism. Unit tests are not optional but it should be part of the code done. #TDD

RT @jitterted@twitter.com
@schmonz@twitter.com I'll accept the premise: writing tests _should be_ hard. That's the hard thinking that needs to be done at some point. TDD doesn't double the time/effort, because that assumes the coding part is _also_ hard, when it's often _much easier_ after having the test in hand.

RT @schmonz@twitter.com
@logosity@twitter.com @jitterted@twitter.com @GeePawHill@twitter.com "REPL with a memory of desired outcomes" is going to be a handy phrase.

Well to any one who watched that live stream. I apologize, it was completely worthless.

Ok Live now #emacs #php https://meet.jit.si/EmacsIsGreatLiveSTream

https://www.youtube.com/c/YisraelDovL/live

So I hope this actually goes out. Hope to do some more live programming with #emacs #php and setting up some routing this time with #htaccess. In about an hour. Or you can come and argue with me about your crazy opinions, that are obviously wrong, just no one ever questioned you about them. Getting #caffeine and #nicotine now.

כל שנה ביום הזה אנו מודים לבורא שזיכה אותנו לגור בארצינו הקדוש. היום לפני 15 שנים.

RT @yonkeltron@twitter.com
I didn't use to be such a fan of TDD. Then I tried it.

RT @yonkeltron@twitter.com
Linters are great because they institutionalize the team's coding standards and preferences in automation.

Code formatters are great because they eliminate arguments all together.

My answer to Why are there so many text editors? https://www.quora.com/Why-are-there-so-many-text-editors/answers/142571970?ch=2&share=0b96cb11&srid=npnQ

Read and use the gitlab work flow. Some things maybe over your head, so read it again and read the git documentation for concepts that you don't understand.

This is one of the best documents I've read on using git properly and productively. 

https://docs.gitlab.com/ee/workflow/gitlab_flow.html

You have things in your git repo that don't belong there. Things like '.env'  are environment specific, and worse, most of the time will expose private info. Things like "vendors/"  are external packages, these also should not be in your  repo. When you started a laravel project both of these should have been in the '.gitignore'  file. 

I don't see that you are using branches, but you are committing "works in progress"  to master.  You should commit often, but master should be reserved for code that is finished. Do your work on a "feature branch"  then when it is done make a merge commit into master. 

#git

You need to improve your git skills. 

Most of your commit messages are meaningless, like "update".  If you are using the same commit message twice,  that is a bad sign. 

@xahlee what do you think about this #mechanicalkeyboard?

https://drop.com/buy/mistel-barocco-md650l-mechanical-keyboard

RT @unclebobmartin@twitter.com
Large and long term refactorings are an occasional reality; but they need not be scheduled tasks. Developers need to learn the trick of gradually changing the design while regularly releasing business value.

TDD is the essential enabling discipline.