• Visitors can check out the Forum FAQ by clicking this link. You have to register before you can post: click the REGISTER link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. View our Forum Privacy Policy.
  • Want to receive the latest contracting news and advice straight to your inbox? Sign up to the ContractorUK newsletter here. Every sign up will also be entered into a draw to WIN £100 Amazon vouchers!

Todays rubbish job £18.12 per hour

Collapse
X
  •  
  • Filter
  • Time
  • Show
Clear All
new posts

    #21
    Originally posted by Freamon View Post
    Shudder. Sounds like the sort of thing that is built as a stop-gap but ends up in production use for 10 years, "enhanced" by a string of people who ultimately vanish leaving hundreds of linked spreadsheets to later be untangled by a poor unsuspecting systems replacement programme.
    It doesnt use spreadsheets in that way, like I said its purely for the presentation layer. So nothing links to nothing, it opens a blank workbook and runs queries and pushes them into worksheets, formats them , collates them, makes graphs of them etc etc.

    Before this, someone would manually run a query, paste it into a spreadsheet, he would then sort it by customer, insert rows , add formulas, make graphs etc etc It took him 3 hours so he only did it once a week. So their data was mostly out of date and no one trusted it. My system runs in 90 seconds.

    Yes they will probably be using it for 10 years as it does everything they want it to and yes I do tend to end up being the person they dont want to let go. As everyones problem the answer seem to be me, not happy about that though.

    Comment


      #22
      Originally posted by escapeUK View Post
      It doesnt use spreadsheets in that way, like I said its purely for the presentation layer. So nothing links to nothing, it opens a blank workbook and runs queries and pushes them into worksheets, formats them , collates them, makes graphs of them etc etc.

      Before this, someone would manually run a query, paste it into a spreadsheet, he would then sort it by customer, insert rows , add formulas, make graphs etc etc It took him 3 hours so he only did it once a week. So their data was mostly out of date and no one trusted it. My system runs in 90 seconds.

      Yes they will probably be using it for 10 years as it does everything they want it to and yes I do tend to end up being the person they dont want to let go. As everyones problem the answer seem to be me, not happy about that though.
      Oh, in exactly the same way that I would get access to do it. Except what I do is easier for the business to support and easier to audit.
      Rule Number 1 - Assuming that you have a valid contract in place always try to get your poo onto your timesheet, provided that the timesheet is valid for your current contract and covers the period of time that you are billing for.

      I preferred version 1!

      Comment


        #23
        Originally posted by escapeUK View Post
        Well, as someone who writes systems from scratch and integrates them with other peoples systems / databases to me its easy.

        I dont tend to do much VBA as I find it a bit amateurish, and I prefer to write my code as a stand alone program that then drives the spreadsheet (if a spreadsheet is needed as the presentation layer.) My current client coined the term "Escape's magic spreadsheets" which I quite like. Some of my recents programs live in the system tray in the same way that MSN messenger does and are automatically rerunning queries every 15 minutes (to give such figures as order intake for instance), which then drive the spreadsheets if someone wants more detailed info.

        Easy is relative.
        Indeed. It's one thing to import an Excel s/sheet into a new db.

        Try modding out a brand new DB schema with several dozen tables, PK and FK constraints, sprocs containing inner joins/loops/global variables etc, throw in some IS packages for integration with your presentation layer, and THEN we'll see.

        Comment


          #24
          Originally posted by escapeUK View Post
          It doesnt use spreadsheets in that way, like I said its purely for the presentation layer. So nothing links to nothing, it opens a blank workbook and runs queries and pushes them into worksheets, formats them , collates them, makes graphs of them etc etc.

          Before this, someone would manually run a query, paste it into a spreadsheet, he would then sort it by customer, insert rows , add formulas, make graphs etc etc It took him 3 hours so he only did it once a week. So their data was mostly out of date and no one trusted it. My system runs in 90 seconds.

          Yes they will probably be using it for 10 years as it does everything they want it to and yes I do tend to end up being the person they dont want to let go. As everyones problem the answer seem to be me, not happy about that though.
          Once you actually leave and they can't maintain the thing that generates the spreadsheets, they'll just leave that untouched and build any add-ons required by using linked spreadsheets etc. It's basically inevitable.
          "A life, Jimmy, you know what that is? It’s the s*** that happens while you’re waiting for moments that never come." -- Lester Freamon

          Comment


            #25
            Originally posted by BoredBloke View Post
            Oh, in exactly the same way that I would get access to do it. Except what I do is easier for the business to support and easier to audit.
            They have lots of easy to support access apps already, that no one can understand or support and are developmental dead ends.

            Auditing? What is this, Health and Safety?

            Comment


              #26
              Originally posted by escapeUK View Post
              They have lots of easy to support access apps already, that no one can understand or support and are developmental dead ends.

              Auditing? What is this, Health and Safety?
              First of all, you have not said what you write your magic spreadsheets in, but if it is so obscure that only you know it, how do you expect the business to support it going forward and how is it any better for the business than the Access databases that "that no one can understand or support and are developmental dead ends". I thought you said databases were easy - why don't they just get a few £100 per day folk in to take them to bits and understand them. Tell me how they are likely to understand what you do when its all hidden away in code. If you got hit by a bus tomorrow, how long till your spreadsheets move away from being magic to worse than the developmental dead ends because nobody knows how they work.

              Secondly, auditors - many companys have audits of their systems to ensure that they are fit for purpose and correct, especially ones dealing with money.
              Rule Number 1 - Assuming that you have a valid contract in place always try to get your poo onto your timesheet, provided that the timesheet is valid for your current contract and covers the period of time that you are billing for.

              I preferred version 1!

              Comment


                #27
                Originally posted by Freamon View Post
                Once you actually leave and they can't maintain the thing that generates the spreadsheets, they'll just leave that untouched and build any add-ons required by using linked spreadsheets etc. It's basically inevitable.
                Probably, personally I think they should just employ a young permie with a bit of programming experience who can follow what Ive done and make tweeks as required.

                Their history says they wont and will just soldier on regardless.
                Last edited by escapeUK; 2 November 2012, 14:38.

                Comment


                  #28
                  Originally posted by escapeUK View Post
                  Well, as someone who writes systems from scratch and integrates them with other peoples systems / databases to me its easy.
                  I've done a fair bit of interfacing myself and quite enjoy doing it, but it's certainly not something everyone can do.
                  Behold the warranty -- the bold print giveth and the fine print taketh away.

                  Comment


                    #29
                    Originally posted by Sysman View Post
                    I've done a fair bit of interfacing myself and quite enjoy doing it, but it's certainly not something everyone can do.
                    No, but the point I was making doing a bit of vba, excel and powerpoint and creating a few databases wasnt that taxing and if it was a permie job that wages wouldnt have been that unreasonable.

                    Comment


                      #30
                      Originally posted by Freamon View Post
                      Shudder. Sounds like the sort of thing that is built as a stop-gap but ends up in production use for 10 years, "enhanced" by a string of people who ultimately vanish leaving hundreds of linked spreadsheets to later be untangled by a poor unsuspecting systems replacement programme.
                      Shudder indeed. Back in my permie days I was accused by senior management of wanting to reinvent the wheel by proposing a rewrite of such stuff.

                      It was a time bomb a-ticking.

                      Tick tock.
                      Behold the warranty -- the bold print giveth and the fine print taketh away.

                      Comment

                      Working...
                      X