If you have met me or worked with me in the last 15 years or so, you will know that I am pretty mad about the web as a platform, HTTP as a protocol and HTML as a state engine. Add to this the last 6 years or so practising agile techniques while building highly scalable websites and you tend to find that I have fairly unusual views in the field about how to build and architect web applications.
So I noticed an issue with Google Chromium and it not updating the cached entry with new headers on a HTTP 304 response. So I logged the issue last weekend and bang! 6 days later the issue is resolved and I have a new version of the browser on my desktop.
Not only was the process super fast but I watched the fix being discussed then applied. I looked at the code change and the unit tests being updated all as it happened. Needless to same I am very impressed.
So after rediscovering the distraction free editors to write reports, it seemed mad not to use the same environment to update my blog. I really like the fact that the editor only supports plain text and didn’t want to reduce the readability of the plain text by having lots of unneeded markup all over the place.
What I needed was a simple tool to convert my semi structured text into html and then I could just upload that to my blog. Ideally the tool would be a command line tool so I could easily automate the two steps.
So many moons ago I was reading about a fullscreen editor for Mac called WriteRoom. The basic premise is that it is a very limited editor that actively aims to block out all distractions from writing. It achieves this by:
Running fullscreen (so no desktop distractions)
Supporting plain text only (so no styling distractions)
No toolbar
No menubar
No statusbar
A few simple shortcuts to do what you need
Anyway I have been running Ubuntu for a number of years, and had often ran Nano fullscreen in a Gnome Terminal but was curious what might now be available. So a few moments googling and this was the list:
One of the pain points we see on web projects is the divide between client side and back end development. This pain might show itself in a number of ways:
Small changes in the HTML cause lots of tests to fail
Small changes to visual layout require large changes to the HTML which then causes the above
Developers say the work is done but it can’t be signed off as it looks terrible or doesn’t work in certain browsers
CSS or QAs want developer to add ID attributes to lots of elements so they can target them more easily
Now ideally all your developers should be poly skilled and understand javascript / CSS / HTML just as well as they understand java / C# / ruby but often the reality is not quite so rosy.
So if we are working in a world where we don’t have the ideal but still need to get the job done what can we do to reduce the pain?
UPDATE: Jim pointed out that you can access the field via reflecting over the delegate. (See comment) Damn this is a bit like how java does anonymous access to private fields of the parent class. I wonder if you could use this for some nasty security violations as people tend to think local variables are safe from reflection.
After the crazy !@$% with JavaScript yesterday I said to Christian, I bet we can do this with C# lambda. So the challenge was set….
So I was chatting with Christian Blunden about JavaScript, and he asked if it was possible to have private fields in JavaScript.
Now the language doesn’t have a key word but I knew that you could use function scoping to achieve the same affect as I had seen the same thing done using the E programming language.
So at my current client we have a bunch of Devs that are fairly recent converts to Resharper and a bunch of old hats who know IntelliJ or have used Resharper since Version 1. We are pairing but we know different keyboard layouts and don’t want to decrease productivity by making one lot relearn the other layout. So with some searching around I found out how to create new layouts and using a simple macro switch between them.
This could be just verbal diarrhea, but I was watching Autum Watch last night and it struck me that the issues with over fishing and the fishing industry as a whole have a lot to do with all the waste inherent with manufacturing processes that use economies of scale to maximise profits. There is waste all over the industry:
The wrong fish get caught and killed then thrown overboard
Same again for fish the wrong size
Then fish go off or get damaged as they try and increase efficiency by doing bigger catches
Then fish don’t get sold because of changes / floods in the market (another trawler comes in at the same time)
I’m sure there are a lot more and I’d love to know the ratio of fish that make it to one’s plate with number caught. Anyway people tend to think that the only alternative is some tree hugging world where you actually catch the fish yourself. Toyota have shown that there are alternatives that are highly profitable, consumer driven and extremely effective. So the question is could Lean be applied to the fishing industry? Could we have a pull system? And what size buffers or queues would we need for it to work?