The Lounge is rated Safe For Work. If you're about to post something inappropriate for a shared office environment, then don't post it. No ads, no abuse, and no programming questions. Trolling, (political, climate, religious or whatever) will result in your account being removed.
Pck is about to have a tool that lets you automatically set the release version you're using based on the available releases published at github.
The versions are super low below because these are temporary while I'm building and testing
pckver [/update [<major>.<minor>.<build>.<revision>]
Updates the Pck binaries from GitHub or displays the available versions.
Current version: Pck v0.0.0.1
Pck v0.0.0.1 (offline only)
It automatically retrieves everything and updates the apps. I think that's pretty neat.
When I was growin' up, I was the smartest kid I knew. Maybe that was just because I didn't know that many kids. All I know is now I feel the opposite.
Such a thing I did, sort of, before the company went VM for almost every user. This ran from an area I carved out on a local server.
My applications would be installed and updated by the same application - it was actually a launcher which, prior to launching the application, would check a script of instructions.
For simple updates, it would compare file dates - but it also allowed roll-back, adding and deleting files and folders, and even total removal of itself, all based upon a script. One of the items in the script that was updated was the script, itself, which allowed not only for updates being added for newly installed files (for example) but even recursive construction. Uploading a new script version would trigger rerunning the entire procedure (unless disabled).
In case you do build your updater, you may wish to incorporate any of the above you may not yet have considered adding (or shun them, as appropriate).
With the VM's it all went away as the keepers of the server and it's "Golden Image" became the method for updates. Very much less efficient.
This gave me control of the code and made changes easy - no copies or instructions or anything. If you used the application is updated. If you didn't use it then it didn't matter. Interestingly, due to some built-in defaults, you could miss a series of updates and still catch up in one step plus, at most, one new script and a rerun.
The point is that being motivated by lazy should not be underrated!
A lazy programmer would just copy/paste.
A lazy programmer names his variables x, y and z because (s)he can't be bothered.
A lazy programmer doesn't think about the structure of his code.
A lazy programmer does the same thing over and over because learning something new is too much of a hassle.
Really, calling lazy the pinnacle of our craft does us ALL a disservice!
It's "myths" like this that attract bad programmers to our field and managers that hire them.
Unless you think all your hard work of figuring out LLR and LALR parsers and then putting that into code was just some lazy Sunday afternoon pastime comparable to watching Netflix in bed
That's kind of the definition of lazy: unwilling to work or use energy.
There is no good kind of lazy when it comes to work.
When programmers talk about "lazy" what they really mean is "well thought out, which took years of training and experience to come up with".
But then they go and talk down on themselves by calling it lazy
It's really hard to NOT create a big ball of mud, that's why so many projects fail and need to be rewritten (only to fail again), but somehow when you don't create a big ball of mud and do it right it's cause you're "lazy"
Why not call it "skilled" instead?
"I'm too skilled to do the same thing twice" sounds a lot better than "I'm too lazy to do the same thing twice" and it's the truth too
We all copy and paste from time to time, no shame in that.
I always say it's a right that needs to be earned, because good copy and pasting is difficult too as you need to understand what it is you're copying.