Good log messages can save you a lot of time and frustration while debugging:
โ log.error("No order found for customer")
โ log.error("No order with orderId [%s] found for customer with customerId [%s]", orderId, customerId)
1000 followers. Damn. Thank you!
I appreciate your support on this journey.
As a thank you, Iโm giving away my 53 Principles of Persuasive Writing.
Just,
RT
Follow
Comment โ53โ
And Iโll send you the link.
($29 on Gumroad)
Free for 24 hours only.
My clients pay me $5k/mo to grow their LinkedIn following and drive tons of sales.
I put together 4 viral LinkedIn post templates you can start using today.
RT + Comment "SEND" and I'll DM you a copy.
Must follow so I can DM.
In 41 days, I grew my following from 0-1,000 followers.
With 0 Twitter experience, $0 spent, and 0 engagement groups.
Other courses will charge you for this (I'm giving it out for FREE)
RT + Like + Comment "Send" and I'll send it over.
(Must be following)
"The usefulness of a piece of code has a great deal to do with its impact on the people who will read it. When we write good code, weโre saving them time and effort. Weโre making their jobs easier. Weโre making an investment that will pay dividends day after day, year after year"
There are two kinds of programs:
those simple enough to obviously have no bugs, and those complicated enough to have no obvious bugs
- Some wise person
Code organization is underrated.
When you look at the code of a project and intuitively know which directory and file(s) to focus on, it reduces a lot of cognitive burden.
Conscious effort should be made to ensure source code files are organized and named properly.
Code organization is underrated.
When you look at the code of a project and intuitively know which directory and file(s) to focus on, it reduces a lot of cognitive burden.
Conscious effort should be made to ensure source code files are organized and named properly.