Skip to main content

The Company Video Repo

I was recently making a couple of screencasts at work, and they were of the kind that were magnitudes better at explaining that writing the stuff down, or explaining it orally.

I've also been thinking a lot about how companies like Github try to do all their work asynchronously. The prime example for this is the [idea - mockup/spike/code - pull request] cycle, aka. "every change is a pull request":


From idea to pull request
Now, I've always had a little distaste for electronic communication over things like issue trackers, chat and email when there are so much richer channels available, with face-to-face with whiteboard being the best.

But what if we could just enrich the async channels with this rich media?
A little while ago, I  tweeted that it would be cool to leave a video message or screencast behind with every commit. (Yes, a bit like lolcommits, except it's not just for fun.)

What if we had a repository of videos where it was super easy to upload these things, and reference them in our commit messages, wiki-articles, mails and other documentation/communication?
It's getting easier and easier these days. You can do Google+ Hangouts and record conversations. Instant upload of screencasts to YouTube (also private videos). I'm sure there are a whole bunch of enterprise products that also serve this purpose, but as the technology matures, it will become more mainstream for companies to have their own video vaults, just as they have their own company blog and wiki today.


We still need to make it easier. Buy software for capturing screencasts, get good webcams and microphones, etc.


At several companies I've worked, we would have regular all-hands meetings, where everyone would be gathered into one room and people would present current projects, tech-talks, etc. Needless to say, not everyone felt they had to be there, and especially not right there and then.

What if the speakers could just record it and stream it out on the go, or archive it so people could watch it at their own leisure? Makes sense to me. A lot of large companies like Google are doing this already, but a lot of smaller companies haven't even considered it.

Of course, anything which is async is one-way, and therefore loses the interaction and a lot of value in being so. Then again, you save a lot by not dragging people into meetings, or interrupting them for conversation.

Meetings and conversations still have their place. But we live in a world where being able to work remotely is becoming more and more important, not just for people who want to work from home, but also for companies that want to be able to scale across time-zones, and save the time and gas-money of their employees. Not to mention the environment.

Comments

  1. http://mediabouts.de/index.php/2013/01/inside-out-outside-in-insidrrr-developers-competence-network/

    ReplyDelete

Post a Comment

Popular posts from this blog

Encrypting and Decrypting with Spring

I was recently working with protecting some sensitive data in a typical Java application with a database underneath. We convert the data on its way out of the application using Spring Security Crypto Utilities. It "was decided" that we'd be doing AES with a key-length of 256, and this just happens to be the kind of encryption Spring crypto does out of the box. Sweet!

The big aber is that whatever JRE is running the application has to be patched with Oracle's JCE in order to do 256 bits. It's a fascinating story, the short version being that U.S. companies are restricted from exporting various encryption algorithms to certain countries, and some countries are restricted from importing them.

Once I had patched my JRE with the JCE, I found it fascinating how straight forward it was to encrypt and decrypt using the Spring Encryptors. So just for fun at the weekend, I threw together a little desktop app that will encrypt and decrypt stuff for the given password and sa…

Managing dot-files with vcsh and myrepos

Say I want to get my dot-files out on a new computer. Here's what I do:

# install vcsh & myrepos via apt/brew/etc
vcsh clone https://github.com/tfnico/config-mr.git mr
mr update

Done! All dot-files are ready to use and in place. No deploy command, no linking up symlinks to the files. No checking/out in my entire home directory as a Git repository. Yet, all my dot-files are neatly kept in fine-grained repositories, and any changes I make are immediately ready to be committed:

config-atom.git
    -> ~/.atom/*

config-mr.git
    -> ~/.mrconfig
    -> ~/.config/mr/*

config-tmuxinator.git  
    -> ~/.tmuxinator/*

config-vim.git
    -> ~/.vimrc
    -> ~/.vim/*

config-bin.git   
    -> ~/bin/*

config-git.git          
    -> ~/.gitconfig

config-tmux.git  
    -> ~/.tmux.conf    

config-zsh.git
    -> ~/.zshrc

How can this be? The key here is to use vcsh to keep track of your dot-files, and its partner myrepos/mr for operating on many repositories at the same time.

I discovere…

The End of GitMinutes (my podcast)

I'm just about ship GitMinutes episode 46, which is going to be the final episode. I'll just paste the outro script here, as it sums up the sentimental thoughts pretty well:

I’m happy to have finally finished [publishing the last episodes from Git-Merge 2017], just in time before Git-Merge 2018 takes place in March. I won’t be going there myself, so I’m counting on someone else to pick up the mic there.

It’s sad to be shipping this one as it is probably the last GitMinutes episode ever. To go a bit down memory lane, 6 years ago, my daughter was born, and as I used a little of that paternity leave to set up my podcasting infrastructure and produce the first few episodes. Initially it was just going to be 10 episodes and call the experiment finished. Instead, I got to 46 episodes, the last dozen or so lazily tailing the last few Git-Merge conferences.

To every one of my guests, thank you so much again for coming on to share your passion in this little niche of computer science a…

Joining eyeo: A Year in Review

It's been well over a year since I joined eyeo. And 'tis the season for yearly reviews, so...

It's been pretty wild. So many times I thought "this stuff really deserves a bloggin", but then it was too inviting to grab onto the next thing and get that rolling.

Instead of taking a deep dive into some topic already, I want to scan through that year in review and think for myself, what were the big things, the important things, the things I achieved, and the things I learned. And then later on, if I ever get around to it, grab one of these topics and elaborate in a dedicated blog-post. Like a bucket-list of the blog posts that I should have written. Here goes:
How given no other structures, silos will grow by themselves This was my initial shock after joining the company. Only a few years after taking off as a startup, the hedges began growing, seemingly almost by themselves, and against the will of the founders. I've worked in silos, and in companies without the…

Always use git-svn with --prefix

TLDR: I've recently been forced back into using git-svn, and while I was at it, I noticed that git-svn generally behaves a lot better when it is initialized using the --prefix option.

Frankly, I can't see any reason why you would ever want to use git-svn without --prefix. It even added some major simplifications to my old git-svn mirror setup.

Update: Some of the advantages of this solution will disappear in newer versions of Git.

For example, make a standard-layout svn clone:

$ git svn clone -s https://svn.company.com/repos/project-foo/

You'll get this .git/config:

[svn-remote "svn"]
        url = https://svn.company.com/repos/
        fetch = project-foo/trunk:refs/remotes/trunk
        branches = project-foo/branches/*:refs/remotes/*
        tags = project-foo/tags/*:refs/remotes/tags/*

And the remote branches looks like this (git branch -a):
    remotes/trunk
    remotes/feat-bar

(Compared to regular remote branches, they look very odd because there is no remote name i…