It has been an enlightening experience growing up in Britain during the Information Revolution...
One of my TaskFactory procrastination tasks over the last few years involved digitising my small pool of CDs and vinyl and pulling the resulting tracks into iTunes.
In previous posts we have concentrated on creating our first unit test. Today we'll look at a simple Dependency Injection example in C# and why this allows us to create better testable code.
In a previous post we covered an introduction to Test Driven Development. In brief it is a process by which a programmer can create simple, automated tests which capture application logic and allow for sections of the code to be continually validated.
...so after many days of furious coding the final feature is completed. The quality assurance team have okay'd the change and a gold release candidate is ready to hit the shops. In the meantime some team members tidy up the code, the final master disk is burnt and sent to fabrication plants in some far off land. A few days later, all is good in the world, you're sitting on a beach somewhere hot with a Cuban cigar and a mojito when a mustachio'd waiter trots up to your sun lounger carrying an inordinately shiny silver platter with a strangely out of place bakelite phone gently ringing. \"For you sir...\"
I've been a Microsoft Windows user for a while, and after some mishaps with traditional Windows laptops ended up migrating to running Windows on a Macbook using Bootcamp. Recently...
After one too many issues with a Hackintosh and a short but painful trip to an Apple store my MediaWiki< Windows installation needed moving across into the unknown realms of OSX.
When I was a child I felt that I had a mind like a steel trap, any fact that made it through my conscious barrier would be there forever. I took no photos since my memory would suffice, and taking photos was too invasive anyway... As I grew older I realised that rather like someone suggesting that 640 KB would be enough memory for anyone my younger self had failed to comprehend the sheer amount of data that would pass through my grey matter during my working life. As a computer professional I can honestly say that I have not stopped learning since I was even younger than the young self above, with new code, facts, problems and processes presenting themselves quite literally every day.
Have you ever encountered this; You've spent some time analysing a problem or investigating an issue and want the process you took or the results of the analysis available in a searchable form at a later date...
Hello my name is FuncRandm, and I'm a Unix user. Its been a few years since my last dose, and I'm trying to fathom what happened since then.
I thought I’d look at securing Hg through Abyss, turning on pushing and pulling through security and what it takes to sort out a backup. I wanted to look at CVS and SVN which I’ll leave for another time.
Like most programmers I have a workflow which allows me to type code at one end, and a seamless, bugfree application will pop out of the other ;).