I’ve tried a few solutions for using multiple computers (mostly one MacBook plus one or two Windows machines) simultaneously and I’ve currently landed on http://synergy-project.org/ as the One for Me.
It’s very good. It’s pretty seamless (last year less so, this years seems perfect) : put 3 machines next to each other, move your mouse across the 3 screens, and control and type into whichever computer has mouse focus. It’s particularly a good solution when some of your machine are laptops and you want to use the laptop screens.
Alternatives I’ve tried:
- VNC and remote desktop style solutions have worked best for me when I have multiple monitors on a single machine. The irritation is when your local monitor isn’t as big as you want for the remote machine and you end up with a scrolling window. The itch that remote desktop solutions don’t scratch though is when some of your machines are laptops, and then you want to use the laptop screen. Of the various options, TeamViewer and MS Remote Desktop seem the fastest; I haven’t yet seen a fast solution for Mac.
- When I don’t need a gui, I find
ssh or similar is really good. Even a modest monitor easily has room for multiple console windows. A reminder perhaps that guis are not always the bee’s knees.
I.T. is not the only industry to have happily latched onto the the former Secretary of State’s famous phrase, “the unknown unknowns”. It’s a useful phrase to ponder if you’re responsible for planning or estimating anything because planning & estimating always involve risk. A recent slideshare by Danni Mannes on Agile Architecture pointed out to me that one should really consider the full matrix:
||Things we know, and we know we know them
||Things we know but don’t realise we know them; tacit knowledge that we take for granted. Become a problem if we are responsible, and fail, to communicate them to people who don’t know. Also a problem when we start work in a new context and don’t realise that what we ‘know’ is no longer valid, so they become unknown unknowns.
||Things we know that we don’t know. We can record the risk, and estimate a cost for investigation & discovery
||Things we don’t know that we don’t know. This is the quadrant most likely to shipwreck plans.
My personal takeaway from this is that I will try using this quadrant when listing risks. Just having a space for the possibility of unknown knowns & unknowns can be an impetus to do a little risk-storming & consultation, to help you discover the as-yet-unknowns.
I’ve just read the brief and brilliant mcfunley.com/choose-boring-technology
We had a debate&discussion at XP-Man on NoEstimates for which I did some notes. Reading the NoEstimates stuff, I was most attracted to the sense of “Let’s not be satisfied with second rate” and of a thirst for continuous improvement.
I was left with the sense (possibly because I already believed it) that there are contexts in which NoEstimates works, and contexts in which it doesn’t. But I was very glad to be provoked to ask in each case, “What value if any is our estimate/planning effort adding?” and “Isn’t there a better way to deliver that value?”
What is an Estimate?
An estimate for a Project is (1) a list of things to work on; (2) a cost-range for those things; and (3) a list of risks, that is (3a) of Dependencies that 1&2 rely on, and (3b) of things that might cause significant change.
An estimate or plan for a sprint is (1) a list of things to work on, (2) a “cost” (eg story points) for those things and (3) a list of things we are uncertain about, or (4) need to get help with.
The value of a project estimate is to feed-in to (1) A go/no-go decision and (2) seeing things we want to see sooner rather than later (e.g. should we hire more people, do we need help from specific 3rd parties, is releasing in time for Christmas possible)
The value of a sprint estimate is, to see things we need to ask for in advance (ie external help or resources); to give everyone a sense of confidence about what we’re doing; to fail-faster, that is to see sooner what we can’t achieve.
“Who are we kidding? Apps are built to earn money. They are a product created to generate profit, and there are a number of ways we can get them to do just that. The simplest, and therefore most common method is …”
So says a typical email in my inbox. But. It ain’t true. Apps are also built because people love to build things. Many, many apps – and websites; and Real Stuff; — are built because people love to built things, and if they didn’t have to earn a living they’d still be building things. For some people, earning money is the pesky thing getting in the way of building the apps they’d love to build.