Weekly Log Template: Fill & Download for Free

Surprised no one has mentioned the following three:1. Vero - It let's you send emails based specifically on what a visitor does on your website. Best of all, once your developer installs it, the marketing team can use the app to define, test, and update the triggers.2. RocketBolt - Most email tracking can tell you when someone opens and clicks on a link, but RocketBolt is the only platform I've found that tells you what the person does after the click. Even cooler, RocketBolt tells you the second an important lead comes back to your site -- even if it's 6 months later!3. SendWithUs - A great platfor for rapid messaging iteration. It lets the development team handle the in-app email triggers (e.g. it's been two weeks since a user last logged in), while giving the marketing team the power to control the templates and messaging without needing access to the codebase.

There are so many. But here are some you sure will need:Sales & MarketingMarketing budget template: Premium Marketing Budget TemplateGrowth action plan: Free 90 Day Plan Of Action for new growthProposal template: Free Sample Marketing Proposal TemplateSocial media strategic plan: Free Social Media Strategy PlanHR:A non disclosure agreement for your employees: Free Non Disclosure Agreement TemplateA employee review form: Premium Employee Performance Appraisal TemplateWelcome letter: Free Welcome Letter New EmployeeHead hunting contract: Premium Head Hunting AgreementA interview letter: Free HR Interview Invitation LetterWorking hours template: Free Working hours Timesheet TemplateEmployment agreement: Free Employment AgreementBusiness travel: Free Business Travel ItineraryFinance:Invoice template: Free Invoice TemplateMonthy expenses budget: Free Monthly Expenses Budget TemplateAccounting journal: Free Accounting JournalCash flow forecast: Free Cash Flow Monthly ForecastIT & SupportITIL: Premium ITIL Change Control Procedure TemplateManagement:Business plan template: Premium Business Plan TemplateTeam meeting template: Free Team Meeting TemplateWeekly status report: Free HR Weekly Status ReportResponsibility template: Premium Responsibility matrix (CAIRO)Project delivery handover template: Premium Project Deliverable Handover Table TemplateRisk management matrix: Premium Risk Management Log and Matrix TemplateProject evaluation form: Premium Project Evaluation Form TemplateMeeting minutes: Free Meeting Minutes TemplateWeekly staff meeting template: Free Weekly Staff Meeting Agenda

Here’s some very general tips for debugging.Get to know your debugger. If it’s not an IDE, learn how to point it at your source files and compilation information required to do source-level debugging. Create a very simple program that calls one routine located in a second source file. Make sure you can set breakpoints and learn to use the core commands. Make sure you know the difference between ‘step into’ and ‘step over’.Program with debugging in mind. In other words,Consider having intermediate values for complex expressions.If appropriate for your language, separate object creation and object initialization.Be cautious about using templates, macros, and other constructs which auto-generate relatively opaque code.Learn the difference between optimized and debug versions of code execution, if they exist in your language. Consider including debug-only code statements for code that only shows up in the debug compilation. For example in C++ you would use #ifdef _DEBUG.Add logging to your program. Use ‘log levels’ which you can configure with a static variable to increase and decrease the amount of information logged for troubleshooting.For any pseudo-random generators used, save the seeds so you can hard-code them if you need to reproduce a particular outcome.Learn how to set conditional breakpoints. As the name implies, conditional breakpoints are only triggered when a condition is set. For example, on a loop from 1 to 10,000, if I know there’s a problem at iteration 7143, I can set a conditional breakpoint for the first statement of the loop when the iterator is equal to 7143. It’s slower than normal execution, but still a HUGE time saver, compared to hitting ‘go’ 7143 times.Learn remote debugging. Many debuggers allow you to remotely connect to a process - even on another machine - and debug it. This is invaluable for debugging full-screen and focus-sensitive applications.If your IDE supports debugging, learn it! If you can build and debug within your IDE, you’ve already got all the source searching tools you’re used to. It’s a great way to go. If you can figure out how to do this with less than a week of effort, you should.There’s tons more, but this is enough for a start. Some tricks which have worked well for me in the past:Binary search. If you have code and simply cannot find the source of a crash or corruption, comment out half the suspect code and see if it recurs. When you find the half it happens in, comment out half of that half, and so on, until you isolate it to a small part of the code. This works for weird compilation issues too.Printing. Never underestimate the power of printing in hard-to-debug code. If you can’t print to a console, write to a file. ideally you’d do this with a DebugLog API.State tracking. Add instrumentation for important variables related to your problem that dumps their values. Seeing the progression of these variable values can help you track down where there’s a logic or arithmetic error.