Originally posted by cojak
View Post
The problems should just come to him at work but he may not be looking out for them. If you do it more than once and it takes any length of time consider automating it. If other people will want consistent changes on the output or need it consistent then consider automating it.
I recently completed a project where we exchanged thousands of assets with another firm, right from the start I automated the csv files and document image extracts, there were 50 odd csv files each with thousands of lines each , the other party changed their mind on the contents of files repeatedly over 18 months. I changed the extract routine for the changes as needed. We also did the same with importing. These both just worked.
The ones where both the businesses had decided to do it manually required lots of rework and turned the go live from pressing buttons to hours frantically struggling in excel, I went out for a walk for hours at a time.
On my own I exported far more data by volume & records than anyone on our side and probably on their side, there was a team of 3 as my opposite number.
Why do I sound cocky about this? Because I told them this would happen up front and we should automate all of it.
My part was seamless so it must have been easy.
Their manual part was making stuff difficult for themselves, guess who got the glory? I did however miss out on the stress!
I intend for the next project coming up to be fully automated with QA,UAT and sign offs because it will be 10-15 times the scope and probably 100+ times the size for data.
With automation I always ask myself - how long will it take to automate , what benefits will I get and when do I get a ROI?
You will be surprised how often it makes sense to automate. The great thing about automation is you can do multiple prototypes and get signed approval reducing risk to the business.
If he is just looking to learn the language then probably get involved in FOSS. That way he can support a project he loves and work with probably some of the best (and worst) coders in the world.
Read Steve McConnell https://en.wikipedia.org/wiki/Code_Complete it helped me structure my attitude to code.
Jeff Attwood & Joel Spolsky of stackexchange fame blogs are great resources. Speed as a feature - genius.
Anyone with other suggestions welcome.
Comment