David RalecheEPISODE 29 RUN TIME 13:59 • Apr 25th, 2017
https://laracasts.com/series/lets-build-a-forum-with-laravel/episodes/29
One of the most important topic a full stack developer should know. This topic will help you to quickly provide quick feedback to your customer within your application
This library Themify is so useful ! Please go ahead and use it
below find an example of icons
try {
while ((line = in.readLine()) != null) {
...
} // while
...
} // try
Although this might make sense for long functions with deeply nested structures, it serves only to clutter the kind of small and encapsulated functions that we prefer.
/* Added by Rick */
Source code control systems are very good at remembering who added what, when. There is no need to pollute the code with little bylines.
source : https://medium.com/@mosquitolwz/clean-code-quotes-4-comments-2de28ba0a6e2
By convention, resource names should use exclusively lowercase letters. Similarly, dashes (-) are conventionally used in place of underscores (_).
Example: /users/{id}/pending-orders instead of /users/{id}/Pending_Orders
Source of information
Using a hyphen in your URLs is recommended by Google, because it makes your website easy to read for humans. As an end result, this means that your site will place better on search engines. Are you looking to learn more about how to improve the SEO of your blog?
I found myself dealing with web server being down, being daily attacked online. My remedy to all of these problems is cloudfare
It has been on my mind for a long time … How to get notified when one of my web properties go down . I found this amazing free website tool called UPTIME ROBOT – Get notified for free and stay on the top of your business
1 - Implement code 2 - DRY (Review Code Improvements) - Do not repeat yourself 3 - Unit Test 4 - Api Documentation + PHP DocBlock 5 - Code Styling PSR-2
There is a difference between hacking and coding. For business purposes developers tended to hack which is profitable for certain situation rather small environments. However when the team grows and when the code needs to be shared, it is ineluctable that some good practice needs to be setup. Unit tests guarantee the stability of your application for every and each incremental release/deployment of your application.
Get the developers to understand that point is critical. Explaining that this practice will allow them not to be blamed after each release, they will be stress free and confident is crucial.
Obviously, this comes with more work since you now need to test your code, and write unit test, making the task more strenuous, but this is indeed HARD WORK
Documenting as well is critical especially if supporting APIs, swagger comes handy for that purpose
lsattr /etc/pgbouncer/users.txt ----i--------e- /etc/pgbouncer/users.txt lsattr /etc/pgbouncer/users.txt ----i--------e- /etc/pgbouncer/users.txt sudo chattr -i /etc/pgbouncer/users.txt lsattr /etc/pgbouncer/users.txt -------------e- /etc/pgbouncer/users.txt vim /etc/pgbouncer/users.txt sudo chattr +i /etc/pgbouncer/users.txt lsattr /etc/pgbouncer/users.txt ----i--------e- /etc/pgbouncer/users.txt
