It helps me to create little rules that provide default decisions for common and unusual situations. A couple of years ago, I wrote down my little rules for working life. Since then, I’ve collected a few more…
Speak the unspoken.
Have difficult conversations.
Find something remarkable, and remark on it, every day.
Not everything needs to be said.
Be intentional: for me, it takes reflection and constant conscious effort for my words and actions to reflect my values.
Consider your influencers (the people who influence you), and choose them as intentionally as you can.
Have a plan. Learn something. Change the plan.
Play the long game. Sometimes we have to do stuff that we don’t care about in the short-term, in order to meet expectations from people who decide if we get paid or if we get privileges. Even while we do the stupid short-term things, we can sometimes set ourselves up for some potentially awesome, or at least potentially meaningful future.
Focus on the outcome. Imagine what happens after you reach your goal. Then what? Often the real goal is the next thing, or the thing after that.
When you hit a wall, step back and learn. Learn more about the problem. Who else sees it as a problem? Who made this wall anyhow? It’s probably there for a reason and the problem might be an unintended consequence.
Get to know the people. The system is made of people, and usually those aren’t the same people who made the system.
Write stuff down. Sometimes what you think you heard wasn’t the same thing other people heard.
Wait a week and ask again. Or a month. Or just listen for the moment when someone else raises the same problem, and chime in.
“Curiosity is the most under utilized tool of leaders” — Amy Edmondson
“Don’t fight stupid, make more awesome” — Jesse Robbins
“Make new mistakes.” — Esther Dyson, 2008 post
Martin Fowler’s talk “The Many Meanings of Event-Driven Architecture” at GOTO2017 provides a good overview of different patterns that all are described as “event-driven” systems. At the end of the talk, he references to an earlier event-driven article, which offers a good prose description of these different patterns that folks are calling event-driven programming. In this talk, he covers specific examples that illustrate the patterns, grounding them in specific applications.
For example: address changed
Scenario: CRM system stores information about people. An insurance quoting system generates insurance rates based on demographics and address. When someone’s address changes, we need to calculate a new value for the cost of insurance.
We often don’t want these systems to be coupled, instead we want a reversal of dependencies. This patterns is used in relatively large scale systems, and also a long-established client-side pattern to separate GUIs and the rest of your code.
The change becomes a first class notion. We bundle the notification + data about the change.
Events OR Commands
* Commands enforce the coupling, it’s very different from an event, it conveys intent
* Naming makes all the diffrence
Additional property → easy to add systems without modifying the original system
Martin notes “the dark side of event notification” where your system quickly becomes hard to reason about because there is not statement of overall behavior.
Event-Carried State Transfer
Named in contrast to REST (Representational State Transfer), the event carries ALL of the data needed about the event, which completely de-couples the target system from the system that originates the event.
Of course, this introduces data replication and eventual consistency (which can be good for some use cases); however, this is a less common pattern since this lack of consistency can actually make the system more complex.
This is one of my favorite patterns which Martin explains nicely in the talk with two examples:
Version control is an event source system for code.
Accounting ledgers track every credit or debit, which are the source records (events), and the balance is calculated from those records.
auditing: natural part of the system
debugging: easy to replay a subset of events locally
historic state: time travel!
alternative state: branching, correcting errors
memory image: application state can be volatile (since persistence is achieved with event log, processing can happen quickly in memory based on recent events that can quickly regenerate state based on recent snapshots)
external systems: everything needs to be an event
event schema: what happens when your data types change?
identifiers: how to create identifiers to reliably replay events
Common (Related) Challenges
**asynchronous processing** can be hard to reason about. This isn’t required for an event sourcing system, yet it is easy to add and needed in most server-side systems. Useful to remember that this is distinct from the core event sourcing pattern.
**versioning** is another option that is quite useful, yet also adds complexity. Greg Young’s advice: don’t have any business logic between the event and the internal representation of a record.
Martin talks about the difference between input event (the intention) and the output event (the effect). In deciding what to store think about how we would fix a bug. The key thing is to be clear about what you are storing, and probably most of the time you want to store both.
Coined by Greg Young, Command Query Responsibility Segregation, is where your write model is different from your read model. Two software components: one for updating the current model (the command component), and one for reading the state (the query component).
Martin suggests that we need to be wary of this approach. A good pattern when used appropriately (which you could say of any model). But isn’t Event Sourcing just a special case of this? Maybe the special case is what provides a structure that make it easier to reason about.
Ghostscript lets you do all sorts of PDF and PostScript transformations. It’s got a command-line tool which is great for page-level operations.
Installation on a mac is pretty easy with homebrew:
brew install ghostscript
The syntax for the commands not very memorable, but easy once you know it. To get a PNG from a PDF:
gs -sDEVICE=pngalpha -o output.png input.pdf
We can also use the API to call the engine from C code. Note: to use this from a program we need to publish our source code (or purchase a license from the nice folks who create and maintain Ghostscript), which seems fair to me. See license details.
What I really want to do is to replace text in a PDF (using one PDF as a template to create another). It seems like all the code I need is available in the Ghostscript library, but maybe not exposed in usable form:
Projects Seeking Developers Driver Architecture was the only place in the docs that I learned that we can’t add a driver without modifying the source code: “Currently, drivers must be linked into the executable.” Might be nice for these to be filed as bugs so interested developers might discuss options here. Of course, not sure that making a driver is a good solution to my problem at all.
There’s an option -dFILTERTEXT that removes all text from a PDF that I thought might provide a clue. I found the implementation in gdevoflt.c with a comment that it was derived from gdevflp.c.
gdevflp: This device is the first ‘subclassing’ device; the intention of subclassing is to allow us to develop a ‘chain’ or ‘pipeline’ of devices, each of which can process some aspect of the graphics methods before passing them on to the next device in the chain.
So, this appears to require diving into the inner-workings of Ghostscript, yet the code seems to be structured so that it is easily modifiable for exactly this kind of thing. It seems like it would be possible to add a filter that modifies text, rather than just deleting it, as long as the layout is unaffected. This implies setting up for building and debugging GhostScript from source and the potential investment of staying current with the codebase, which might not work for my very intermittent attention.