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.
Depends - a "normal" PC eraser may not know that opening a block for read/write may not overwrite the same physical block on eMMC memory for example, because the hardware deliberately writes to a new block as it wears out with writes, not reads.
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
AFAIK, the recommended procedure is to encrypt the device then do a factory reset. The factory reset will erase the encryption keys so everything stored on the device will become unrecoverable random data.
How the store would do it: copy over all relevant files to new device, then perform factor reset on old device. No special software needed for the factory reset, I believe. Their should be a Samsung switch software for android devices, and one similar for iPhones.
Anything that is unrelated to elephants is irrelephant Anonymous - The problem with quotes on the internet is that you can never tell if they're genuine Winston Churchill, 1944 - Never argue with a fool. Onllokers may not be able to tell the difference. Mark Twain
1. peel off any outer cover/pouch,
2. erase phone and place on a shelf,
3. take the previous returned [as much as possible] identical model phone,
4. pop on outer cover/pouch from step 1,
5. scribble something almost readable, sign and attach work order,
6. add a post-it note with with the words "do not return before: [current date + 1 month]",
7. place repaired in the out-tray.
Signature ready for installation. Please Reboot now.
Architectural Principles In Basic Stages
1) When I began learning OOP principles way back in 1993 there was a focus on : reuse via inheritance
2) As OOP principles gained traction many companies, developers and researchers discovered the problems with this and a new idea arose : prefer composition over inheritance
3) Next people began to discover that constructing small services which provide one distinct solution were a good idea. SOA was the buzz-phrase we heard. Of course, there was much truth in there.
4) Now, we are hearing a lot about Microservices. It's another progresssion.
Ideas and Buzz-Phrases
Of course all of these ideas get buzzed by people who don't really even know what they're talking about and then people at the fringes just think,
"Oh, it's another Architect-induced cycle of info-BS."
However, each of these things has contained a core of knowledge that has tried to help us all take another step toward better practices -- to turn software dev from magic/art to science/engineering.
Sometimes: Layers of BS
But a lot of the good stuff does get covered up in layers of BS by uninformed devs.
Must Read: So Many Great Ideas
The reason I'm writing about this is because I've just completed the intro and chapter 1 of a absolutely fantastic book on Microservices where the extremely talented author has summarized all of this and then succinctly and clearly exposes the truth about them as a next logical step in this progression. You must read this.
So Difficult To Get New Ideas
It is often so difficult to get new ideas. It is so rare to find someone who illuminates things so clearly. This author does a great job of providing the architectural overview but also explaining in detail exactly how microservices can solve certain problems.
It's always cool to find new resources like this, especially when they illuminate buzz-phrases that we all hear about.
It really is a great read. I am always happy to find new authors who : 1. open up new ideas / concepts in new ways so I think new thoughts 2. get to the point quickly 3. describe how the technology really works, succinctly 4. give me an idea where architectural principles fit together into the bigger puzzle
I agree with you on that, the book should be to the point, no long stories should be there, i would love to have the list of books from you which you think should be read as a Computer Science professional and Software Developer.
Thanks that's a very nice compliment that you are interested in what I've read.
I will try to get a list going and share it.
Some of the books I've enjoyed are so old like Programming Windows 3.1 by Charles Petzold. That book was just so well written and was like having a mentor sit with you and teach you programming. Of course, now it is not relevant at all.
to turn software dev from magic/art to science/engineering.
It'll never happen. Software development is accessible to the masses, even children. Science and engineering requires a level of formality that programmers try to avoid at all cost, and therefore ignores the cost, and then we companies / OS projects that fling tools/frameworks at us that market their tools as making programming easy, as in, Pink Floyd cue here, "we don't need no education" (reference to Brisingr's post below.)
Would you hire a college dropout (being one myself) to build a bridge? No. But we hire junior developers with no experience in the tools, languages, or formal programming practices to code things that require performance, usability, stability, security, and maintainability, with little or no mentoring or oversight.
A little bit of a negative view, but I do agree that it won't really happen as an entire movement.
It does, however, happen in individuals and those individuals write the best software.
That's also why the book is so interesting because the writer addresses this exact idea and the idea of moving it more toward science/engineering and away from art/magic.
Here's the author explaining that exact point. I think you'll find it interesting.
The Tao of Microservices
Software development is an art. It isn’t predictable enough to be engineering. It isn’t rigorous enough to be science. We’re artists—and that’s not a good thing. We find it hard to work in teams, we find it hard to deliver on deadlines, and we find it hard to focus on practical results. Anyone can claim to be a software developer; opening a text editor is no more difficult than picking up a paint brush. A small number of painters are 10 times better than others. A small number of coders also are 10 times better than others. But most of us are working on bad instincts.
Unlike art, software has to work. It has business problems to solve, users to serve, and content to deliver. We have a thousand opinions among ourselves about how to do things correctly, yet many software projects are delivered late and over budget. Much software, especially that produced by large companies, offers users a terrible experience. We have a self-important belief in our work, as artists, that isn’t connected to the reality of our systematic failure. We need to admit we have a problem, understand the nature of that problem, and use science and engineering to solve the problem.