"Points" were originally a way to talk about effort in a dysfunctional (from an agile-planning perspective) environment that focused on time-based rather than priority-based planning.
This week we'll look at a concrete example of how to use reverse iterators.
If you can bring your human intelligence to bear on that small percentage, sometimes it can have big payoffs.
Last week, we established that pointers can be used to represent boundaries. Let's continue by looking more closely at how these representations interact with reverse iterators.
I found a line of very neat sensors that connect via USB and one of them provides an RFID sensor.
Agile thinking must extend way beyond the boundaries of the Engineering Department for it to work at all.
Let's continue last week's discussion about the relationship between boundaries and pointers.
The idea is to write your top-level program in the form of your high-level requirements or use cases.
Not every boundary has a corresponding element — after all, the sequence might not have any elements at all.
Last time, I showed you how to enumerate serial ports from Qt — a library that works across many different platforms. What I didn’t do was open one of those ports up and do anything with it.