Programming methodologies such as XP (Extreme programming) work very well in some cases but fail very badly in many as well.
For example: I pair-programmed with a data scientists, it was amazing. Lots of nice unit tests, incrementally designed code, worked wonderfully.
Another example: pair-programming with another developer. Constantly fighting over style. In this case, working individually is much better.

Decoupling an application properly allows not only "nice" applications, but also parallelised development, where people don't step on each other's toes.

Presentations and cables....

Such a pain, it is to hook up your laptop to that projector or display for everybody else to see. Typically the cable is thick and short, so you're restricted to using it in only one place.

I had tried Chromecast before but it was terrible but the set up was super clumsy and unreliable. And I believe the case will be similar solutions... I do NOT want to enter any passwords and screw about all the time. This eliminates many semi-cheap solutions with Miracast, AirPlay, etc, etc.

So this only leaves point-to-point solutions. One of such is a transmitter + receiver pair such as C2G - https://www.youtube.com/watch?v=mEsJWkgaGTU / https://www.youtube.com/watch?v=HmP9Xd-MQb4 - or Nyrius ARIES Prime
https://www.youtube.com/watch?v=48F5Ur0mlII - https://www.amazon.com/gp/product/B009E6R89C/

However this stuff is not cheap, some of it requires custom software and the like, which defeats the point. They also require extra USB ports, which is a pain.... https://www.youtube.com/watch?v=48F5Ur0mlII - https://www.youtube.com/watch?v=arz0IfpbT7A - https://www.amazon.com/Cable-Matters-Wireless-Extender-Cables/dp/B01N5P9RJT - https://www.amazon.com/Optoma-WHD200-Wireless-Transmitter-Receiver/dp/B00BPXILY8

This then brought me back to HDMI, and then it hit me: at home I had intentionally purchased a fairly thin HDMI cable due to the fact that other HDMI cables are so inflexible and cause a mess. This then brought me to think that actually all I need for presentations is either direct wireless OR a thin enough HDMI cable that doesn't constrict movement and is small enough to carry around. They are inexpensive and there's plenty of them around.

Perhaps there's one that folds up nicely for easy transport, and now you have a nice portable and interoperable solution. Zero lag, zero software, only need to pay attention to not trip over it. And paying attention is what you should be doing anyway.

Here's the best I found in a short search: https://www.amazon.com/Nanosecond%C2%AE-Super-Extreme-Speed-Cable/dp/B0080JR09C/ref=cm_cr_arp_d_product_top?ie=UTF8

I'm quite pleased with my Git Work <http://git.work/> so far. Originally it was intended to be a portal for getting work, but I decided to simplify it into an aggregator for other portals instead.

One such portal is ScalaWilliam Work - http://work.scalawilliam.com/

So far I paid out $95 ($25, $50 & $20), and have been happy with the results.

Instead of building a large system right up front, I decided to try out something smaller so I could test the idea. I already found some problems that I would've experienced, had I gone into Git Work waterfall-style.

All of the pieces of work I paid for are open source and for my own satisfaction/learning. I'm quite pleased :-)

Post has attachment

Post has attachment
So here's the first Git Issue that I'm making available as part of Git Work (http://git.work):
https://github.com/ActionFPS/ActionFPS-Book/issues/6

While analysing Git Work, I've been thinking how to minimise the surface of the work and simply get to the point. Originally I was thinking about complex validation forms and workflows, but then boiled it down to simply posting an issue on GitHub.

I posted it up on Twitter (https://twitter.com/Git_Work/status/859273198788952064 and https://twitter.com/ScalaWilliam/status/859001004485783553)

I want to make it as flat as possible, as little programming involved, as little hierarchies and log-in forms, and as much reuse of existing systems as possible.

But while linking to these Issues directly, I lose a lot of important information, such as tracking how many people see them. I will not be able to verify how many people visit the page for example. This means that perhaps I won't be able to achieve the flatness that I wish.

Also I don't get to customise much of a view for the paid side of the project either. But nonetheless this is my first "MVP" type of thing.

What could be next? I suppose I could store the list of Issues straight in Git and read from there, so that I don't need an internal database. This stuff is versionable and people can even make pull requests!

Post has attachment
Wait while more posts are being loaded