Joined devRant on 5/26/2016
Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple APILearn More
You know a good way to handle all of the issues with W10 force updating your system? Do it yourself FFS!
You know there are updates. Windows has been telling you ...
Pick a damn time, start the update and go get a coffee, lunch, take a dump or go home for the day.
It's *never* going to be the right time if you don't choose it. It will always be an inconvenience or you'll be "in the middle of something important" and then you'll get all pissy about it.
Ugh. That may have been a mistake.
I'm deep in a large effort to refactor my project. It's a one man deal and something I've been working on pretty much every day in some fashion for nearly 10 years (five years ago I started a scratch rewrite to move from a fully CGI server rendered application to a browser rendered asynchronous version built around JS) and that took me three years.
I started this refactor about 8 weeks ago. Turns out I've been tackling the largest modules and progress has been decent. So that's good.
But I got to wondering ... Just how much code is there?
So I whipped up a quick script to do some calculations. Read each file and get a line and word count, skipping empty lines.
In JS it turns out I have 83,973 lines and 467,683 words.
On the back end, 86,230 lines and 580,422 words.
Average publishing stats say the are about 250 words/printed page.
That means I'm confronting refactoring 1,870 pages of JS. That's the size of several decent sized novels. (I think I've done the equivalent of Maybe 400 at this point).
Makes me feel like the walls are creeping in to know how much is left to go ...
Just got done watching a 2 1/2 hours of Uncle Bob on programming. I really like his style of speaking. Great data and interesting viewpoints. Really easy to follow. I'd read some of his articles, but never listened to him before. Will definitely be watching more. For those of you in organizations using "agile" development and having a tough time of it, his talk called The Land that Scrum Forgot was really interesting.
And he really looks amazingly like my uncle, Tom, who's also been a programmer for decades! So I just think of him as Uncle Tom instead.1
I once worked Tech Support for a point of sale software package. There was really no internal help desk, so we got all of those questions as well.
One day our front receptionist that her computer is being really weird and she can't type - it keeps inserting 3s in the middle of what she is typing.
I take the short walk down the hall to her desk and see that, indeed, a never ending string of 3s is being input to her screen.
"I can't figure out what's wrong." she says.
Then I reach over and remove the edge of an open binder whose edge was resting on the 3 key and enter key on the num pad.
"That should fix it."
Walked back to my desk.1
Oh thanks Windows. I wasn't working. And that Windows 10 upgrade I very specifically confirmed as cancelled ... yeah, go ahead and start that installation with no warning, while I'm working, sitting at a Starbucks that will eventually close and cutoff my ready access to power on a device with limited battery life, probably before you finish the update.
I don't mind sitting here twiddling my thumbs while you do your thing ...
Not that I didn't plan to upgrade, I actually like Windows 10 ... but it wasn't on the agenda for this particular moment.
Wrote a slick scheduling and communication system allowing me to assign photography resources based on time and location.
I'll tell you a little secret ... I'm not actually a dev. I'm a photographer, pretending to be a dev.
Or ... perhaps it's the other way around? (I spend most of my time writing code these days, but only for me - I write the software I use to run my business).
I own a photography studio - we specialize in youth volleyball photography (mostly 12-18 year old girls with a bit of high school, college and semi-pro thrown in for good measure - it's a hugely popular sport) and travel all over the US (and sometimes Europe) photographing.
As a point of scale, this year we photographed a tournament in Denver that featured 100 volleyball courts (in one room!), playing at the same time.
I'm based in California and fly a crew of part-time staff around to these events, but my father and I drive our booth equipment wherever it needs to go. We usually setup a 30'x90' booth with local servers, download/processing/cashier computers and 45 laptops for viewing/ordering photographs. Not to mention 16' drape and banners, tons of samples, 55' TVs, etc. It's quite the production.
We photograph by paid signup only - when there are upwards of 800 teams/9,600 athletes per weekend playing, and you only have four trained photographers, you've got to manage your resources!
This of course means you have to have a system for taking sign those sign ups, assigning teams to photographers and doing so in the most efficient manner possible based on who is available when the team is playing. (You can waste an awful lot of time walking from one court to another in a large convention center - especially if you have to navigate through large crowds - not to mention exhausting yourself).
So this year I finally added a feature I've wanted for quite some time - an interactive court map. I can take an image of the court layout from the tournament and create an HTML version in our software. As I mouse over requests in one window, the corresponding court is highlighted on the map in another browser window. Each photographer has a color associated with them. When I assign requests to a photographer, the court is color coded with the color of the photographer. This allows me to group assignments to minimize photographer walk time and keep them in a specific area. It's also very easy to look at the map and see unassigned requests and look to see what photographer is nearby.
This year I also integrated with Twilio and setup a simple set of text shortcuts that photographers can use to let our booth staff know where they are, if they have memory cards that need picking up, if they need water/coffee/snack, etc. They can also move assignments on their schedule or send and SOS for help if it looks like they aren't going to be able to photograph a team.
Kind of a CLI via the phone. :)
The additions have turned out to be really useful and has made scheduling and managing the photographers much easier that it was in the past.18