The actuality of bit-rot in media is uncertain. Many documents 500 years old are readable-ish if you have the skills and accept that some parts may have decayed. That tells us a lot about te exact media people used way back then.
The trouble with digital records is this:-
Searchability is a requirement (even though we don't expect that with written records). The reason is that there is so much of it when compared with the sparse records of times past. So you need a 'good' copy for data analysis and some original media to inform historians of the future how we looked upon the information, or what 'ordinary people' or 'ordinary businesses' had at their disposal.
Outside You know the rows of path lights typically powered by a solar cell on the top that are a glowworm if you don't have long nights and short days? Well, if they're on a path or steps then make the one at each end responsive to some stimulus, eg the light from an opening door or a IR approach AND have the chain react sympathetically so they all light up one recognising the next's burst into life. This means the light output can be much higher for a short period rather than emitting a miserable glimmer all night. Once proven the tech could be baked in a 2-cent chip. Also the setting-up would give
Inside As a midnight programmer I often want to go downstairs to make a cup of tea etc. My computer room has subdued lighting and I don't want bright lights in the stairs when 3 leds will do. But I would like the simplicity of battery source with automatic operation.
- She is the one who forces the issue with Witch and wizard.
- Her 'friends' are companions who jump on her wagon for their own reasons.
- OK there is some cute/schmaltzy/apple-pie stuff, but she's not growing the lion, tin man etc. but letting them free.
The reason it's a great film is that it has a vulnerable/confused girl becoming feisty and then at the end still lonely. That's the Monomyth writ large.
Snyder's book implies there's ONE way to plot a film. The danger is that this sort of story arc does not fit well with the way females do their heroing. (In short, boys go away to have an exciting time and the story is about them, girls stay at home and deal with whatever has to be dealt with and the story is about how people deal with issues.) A good example of the boy's story is the Wizard of Oz. A good example of the girl's way is the TV series Dad's Army. (There's a reason why the first is a film and the second TV. Notice of course the main protagonists are 'wrong-sex')
So if you follow 'Save the cat!' you'll miss out on lots of interesting plots with powerful characters. I've got an essay on the subject at http://vulpeculox.net/writing/HeroismForGirls.pdf for anyone who wants to compare and contrast.
SOME slashdoters want insights into how to passage the rapids of Information Technology. Possibly MOST. At the least it is about learning from other people's mistakes. So in the middle of a (possibly) heated _discussion_ about foo one or more twerps barge in. They have mouths but not ears. I'll just repeat that: They have mouths but not ears. (Their brains may be a bit tiny as well.) Now if I was in a pub I could stand up and tell them to DIAF and leave their betters to fix problems on behalf of everyone. (IME this works if you have at least one supporter who is fully behind you at the time.) The equivalent in the Internet/Forum/Developer Café is some sort of censorship.
I'm all for it. If you're in the elite then you should open your doors to the others but don't be afraid to 'Blackball' the scum that poison proper and necessary discussion.
Start FIRST with what YOU want to do and WHY it is important to do it your way. Without this motivation you're wasting your time.
If you don't know anything about the architecture of the system then sketch your own over a cup of coffee to find out what are likely to be the key components.
Now you have a goal you can see what parts of the existing system are applicable, missing etc. Your basic knowledge of the inside cogs, wheels and not forgetting irrelevant bells and whistles will be a great help in focussing on elements, themes or modules. (For example the original might be full of cruft concerning what you regard as a dead-end but the original developers considered a bonus feature.) With the knowledge gained from the original system you may be able to look upon it as a prototype and build a much simpler system that isn't full of serial adaptations.
If you have a 'porting' job then there are probably tools to at least highlight places to deal with.
This is the sort of mental challenge that should be bread and butter to programmers, can be set at different levels of difficulty and provide a diversion from our own bloody code-knots. The emphasis to be on coding algorithms rather than stupid bugs or quirks.
I'm curious too know if there is a home for such puzzles, people have examples and if anyone would be generally interested."