This post follows on from lesson 4 in this series of posts.
Hopefully you’re no longer fearful of the debugger, and are curious to learn more debugging techniques.
In this lesson you’ll learn more about the use of breakpoints to help you reach points of interest more quickly.
This post follows on from lesson 3 in this series of posts.
You should be comfortable navigating through code and inspecting interesting variables as you go.
Next you’ll learn how to view the files you are debugging without leaving the debugger.
This post follows on from lesson 2 in this series of posts.
If you’ve followed the lessons so far you’ll have some basic knowledge around starting the debugger and examining variables.
It’s time to find out how to descend into the depths of some code, stepping into functions.
This post follows on from lesson 1 in this series of posts.
Now that we understand how to run, and quit the debugger it’s time to inspect some data.
On April 3rd, I went to Shoreditch Works Village Hall for the London Mobile Forum 2.0 hosted by Facebook. It was a single-room, single-track, “intimate” affair with only about 60 attendees, and I enjoyed it immensely.#
This post follows on from the Introduction to the perl debugger post.
If you haven’t already read the Introduction, please read it first, as it will help you to get set up, and understand how to work through this lesson.
Some of our internal web applications are low-traffic enough that a
preforking server can handle them without difficulty. Some others, on
the other hand, can really benefit from a non-blocking implementation,
so that each server process can serve multiple requests “at the same
time”, by working on a request while waiting for other services to
return data for other requests.
Up to now all our non-blocking web services were written for the JVM,
usually with the Akka framework, but I wanted to see how hard would it
be to build something similar in Perl.
Turns out, it’s not very hard at all, if you use the right libraries
and pay attention at a few tricks.
If you use sandboxed-module to stub or mock module dependencies when unit testing your Node.js code, you probably already know it supports istanbul code coverage metrics.
Last week, I went to give a talk about
SBJson (an Objective-C library
for JSON parsing and writing) to the
London iOS Developer Group. They
meet on the first Wednesday of every month at the Regent Street Apple
store for technical talks, followed usually by a social event at a
nearby pub. In my talk, I tried to explain why I think SBJson is still
relevant—even after Apple added native JSON support to iOS 5
In today’s tech forum, I locked the doors and started teaching some of the perl developers the basics of the perl debugger.