Monday 4 May 2020
Automate & Scale Your Lead Generation Today - Find & Engage With Your Prospects
Automate & Scale Your Lead Generation Today - Find & Engage With Your Prospects: https://sotonmedia.com/linkedin-automation-tool-so/
#linkedinleadgeneration #leadgeneration #marketingtips
Thursday 23 April 2020
⭐️Lead Generation Tool REVEALED⭐️
⭐️Lead Generation Tool REVEALED⭐️- Automate & Scale Your Lead Generation Today: Find & Engage With Your Prospects: https://sotonmedia.com/linkedin-automation-tool/?social
#LinkedIn #Leadgeneration #marketingtips
Tuesday 25 February 2020
Linked In Automation Tool
Hi, I found a great LinkedIn Automation Tool to help with Lead Gen.
It sends personalized:
- Connection Requests,
- Follow up Messages, and
- Drip Campaigns,
to highly targeted lists of potential prospects.
If this is of interest, you can try it for free at:
https://sotonmedia.com/linkedin-automation-tool/
I hope this is helpful. Br, Andy
Friday 22 November 2019
New Website: FreeUKCompetitions.com - Free UK Competitions You Can Enter Now Online
Hello,
I've Just Launched a New Website, Solely Focused on Free UK Competitions.
Please Check it out and Let Me Know What You Think? Thanks.
Free UK Competitions You can Enter Now Online!
All the Best, Andy
I've Just Launched a New Website, Solely Focused on Free UK Competitions.
Please Check it out and Let Me Know What You Think? Thanks.
Free UK Competitions You can Enter Now Online!
All the Best, Andy
Monday 26 November 2018
How to Clear Error & Access Logs on Ubuntu 16.04 Apache Server
Here is an example of the terminal commands to clear error logs and access logs. Remember to update the file paths to the location of your error/access log/s.
Original Article Posted On: https://andycorby.com/clear-error-access-logs-ubuntu-16-04/
sudo bash -c ‘echo > /var/www/html/logs/error.log’sudo bash -c ‘echo > /var/www/html/logs/access.log’
Original Article Posted On: https://andycorby.com/clear-error-access-logs-ubuntu-16-04/
Some Programming Best Practices for Productivity
Here are some of my thoughts on programming best practices to improve productivity.
YAGNI: “You Ain’t Gonna Need It”. Don’t write code that you think you might need in the future but don’t need yet. This is coding for imaginary future use cases and the code could become dead code or need rewriting because the future use case could turn out to work differently from how you imagined it.
Comments & Console Logs: When comments are used they should be used to explain why the code is there, not what it’s doing as that can be read in the code itself. Blocks of commented code shouldn’t exist in productions releases. This is also true for testing console log statements which should not make it to production releases.
Testing: Test all changes. Only if there is a very good reason should code be left untested. Lack of time is not a good reason and can end up costing more time. Possible good reasons include: genuinely un-testable (in any meaningful way), impossible to hit in practice, or covered elsewhere in a test. Code without tests is a liability.
Code is the Enemy: Code can go wrong and it needs maintenance, so try to write less code, delete code, and don’t write code you don’t need.
Write Defensively: Always think about what can go wrong, what will happen on invalid input, and what might fail, this will help you catch many bugs before they happen.
DRY: “Don’t Repeat Yourself”. If the same code is being repeated multiple times consider putting it in a reusable function. This is more important in production files and not as important in test files, keeping code and what could go wrong in the production environment to a minimum.
Correct VS Speed: Make code correct first and fast second. The top priority is to write code that works and has been confirmed with test. The second priority is the performance and speed of the code (within reason, provided it is not excessively slow code which will cause issues).
Standard Format: It is good to have a standard format (use of indentation, spaces, blank lines, comments) all developers on a project work to, in order to help improve fast readability and help reduce development time.
Original Article Posted On: https://andycorby.com/some-programming-best-practices-for-productivity/
YAGNI: “You Ain’t Gonna Need It”. Don’t write code that you think you might need in the future but don’t need yet. This is coding for imaginary future use cases and the code could become dead code or need rewriting because the future use case could turn out to work differently from how you imagined it.
Comments & Console Logs: When comments are used they should be used to explain why the code is there, not what it’s doing as that can be read in the code itself. Blocks of commented code shouldn’t exist in productions releases. This is also true for testing console log statements which should not make it to production releases.
Testing: Test all changes. Only if there is a very good reason should code be left untested. Lack of time is not a good reason and can end up costing more time. Possible good reasons include: genuinely un-testable (in any meaningful way), impossible to hit in practice, or covered elsewhere in a test. Code without tests is a liability.
Code is the Enemy: Code can go wrong and it needs maintenance, so try to write less code, delete code, and don’t write code you don’t need.
Write Defensively: Always think about what can go wrong, what will happen on invalid input, and what might fail, this will help you catch many bugs before they happen.
DRY: “Don’t Repeat Yourself”. If the same code is being repeated multiple times consider putting it in a reusable function. This is more important in production files and not as important in test files, keeping code and what could go wrong in the production environment to a minimum.
Correct VS Speed: Make code correct first and fast second. The top priority is to write code that works and has been confirmed with test. The second priority is the performance and speed of the code (within reason, provided it is not excessively slow code which will cause issues).
Standard Format: It is good to have a standard format (use of indentation, spaces, blank lines, comments) all developers on a project work to, in order to help improve fast readability and help reduce development time.
Original Article Posted On: https://andycorby.com/some-programming-best-practices-for-productivity/
The Great Firewall of China – SSL Certificates
When Search Engine Optimising a Chinese website for the main Chinese search engine Baidu, there are benefits to having a .cn domain name and having a server located within the Great Firewall of China.
From what I understand the Chinese government censors web pages by intercepting the connection between a server and the end user. If a web page does not pass their censorship then the page could be edited or not displayed to the user.
Whilst having an SSL certificate protects users data it can stop the Chinese government from censoring individual web pages so if a page does not pass censorship then a whole website may be blocked. Therefore, you may want to consider your SSL set up carefully and whether you will force HTTPS when setting up a server within the Great Firewall of China.
Useful Article: https://jpgamboa.com/ssl-usage-china/
Original Article Posted On: https://andycorby.com/the-great-firewall-of-china-ssl-certificates/
From what I understand the Chinese government censors web pages by intercepting the connection between a server and the end user. If a web page does not pass their censorship then the page could be edited or not displayed to the user.
Whilst having an SSL certificate protects users data it can stop the Chinese government from censoring individual web pages so if a page does not pass censorship then a whole website may be blocked. Therefore, you may want to consider your SSL set up carefully and whether you will force HTTPS when setting up a server within the Great Firewall of China.
Useful Article: https://jpgamboa.com/ssl-usage-china/
Original Article Posted On: https://andycorby.com/the-great-firewall-of-china-ssl-certificates/
Subscribe to:
Posts (Atom)