I am starting a series of posts based on the mentoring I do for new engineers. When mentoring engineers it is important to teach both specific skills, problem solving, and mental models. The first two are self-explanatory evolutions of the basic skills of engineering. By “mental models” I mean ways of framing a situation, such as from a customer point of view or a product manager view, which can help one think about the correct handling of a situation.
Some of these points are from my own thoughts and conversations but I don’t own them nor are they wholly original to me. Some points come from my current and past managers who have helped me grow as a leader and engineer. Some are from materials and discussions from the MBA I completed last year. Some are from readings on the internet. To summarize: I don’t own this knowledge. I am sharing it and I hope anyone who encounters it will share it as well and contribute comments, feedback, and other ideas.
It would be really interesting if a hacker found a way to harvest new passwords and passwords being changed and faked a huge data breach to get millions of people to change their passwords.
Threatening fake data breaches if not paid a ransom could be the next profitable hacker market. It would probably work a few times, and certainly muddy up the waters for both organizations and people. Imagine trying to figure out how to respond when 10 major groups have a data breach per week, but 2 of those are real and the rest are fakes. Chaos and massive frustration.
Wikis are interesting. I love the page interlinking and editable nature of them. In the past I have used TiddlyWiki for a personal wiki long before Evernote or OneNote came along. That must have been back in 2004–7, though I check in on it now and then. It is a single HTML file that works like a wiki, modifying itself. It is very impressive. It makes it easy to sync via DropBox too and backup as snapshots in time.
I just visited that link for the first time in a year or two though and found it’s been revamped, modernized, and updated. It looks great! Might have to play with it again.
However today I came across 3 other wikis that I may want to use for my personal notes or for ArtsFuse knowledge sharing with my colleagues. I don’t know much about them yet other than the current trend is to use git for data storage and be easily hostable with nginx on a python/ruby backend.
Realms - Git based wiki written in Python Inspired by Gollum, Ghost, and Dillinger. It is Markdown-only which is a painful limitation. But it has live collaborative editing.
Branchable — This is a hosted solution starting at $10/month
Gitit — Git-based wiki that can be edited in many markup languages and export to many more including PDF, EPUB, and MediaWiki format.
If these can be customized without a ton of effort I may try them over OneNote which is my current favorite. Wikis may be a better solution to sharing knowledge with coworkers than shared OneNote folder, but they also have to compete with Dropbox and Google Drive for collaboration.
Updated August 25, 2014: ArtsFuse has rebranded! I updated the links below to point to artsfuse.com instead of old artsmuse.io website.
The redesigned ArtsFuse website is live. This is the side project I am working on with my wife and my friend Steve: a customizable art delivery solution for the home and office. What does that mean? It means we can put art on any TV!
Anyway, I redesigned our page. Below is a screenshot of the new front page. The goal is to quickly get visitors to useful content on one of the 3 landing sites for I want art, I make art, and I display art.
Screenshot of revamped ArtsFuse main website page.
We are using Jira more and more at work and I am finding it very frustrating. As an issue tracker it works well and links nicely with the other Atlassian products we use, like Crucible. But now we are using it for agile iteration tracking and it is just a stream of half-baked behavior.
Atlassian has put lots of effort towards creating an ajax-heavy UI, but each action is as slow as a full page load. Then things that seem to be first-class artifacts (Iterations) can’t be directly searched and linked-to without dropping into their SQL-like query syntax.
You have to get the actual iteration ID by clicking the Iteration from within in a story and it changes from “iteration 1″ to some ID, in this case 2656. Then you can construct a search filter based on that and filtering out subtasks:
sprint in (2656) and issuetype in standardIssueTypes()
Then you can get a permanent link to it. They are predictable after that, but for each iteration you have to locate this ID and construct a new query. There seems to be no Iteration History type view or even a way to directly open them and look at them historically. Iteration doesn’t seem to be a first-class concept, just a glommed-on bit of UI wrapping.