|
a. Between 7-8
b. Between 7-8
c. Between 2-8 (less than 2 or greater than 8 make them hard people to work with)
d. It does some. If I am writing an example to help someone, It will be sparse on rule following. If it is an answer on StackOverflow or CodeProject, it may push toward following the rules more in order to be a more correct answer. If it is code that I have any possibility of fixing bugs in or doing maintenance to, I will be liberal in documenting and making the code as readable and maintainable as possible. Since I am 62, forgetfulness is a driving force for this. High level and low level are no different at all.
|
|
|
|
|
If noone sees my code except me, is it still sh*tty code?
"(I) am amazed to see myself here rather than there ... now rather than then".
― Blaise Pascal
|
|
|
|
|
a) 6-7. If you don't ship code in a timely manner, there's no paycheck. If you can't add new features in a timely manner, there's no paycheck. If you get the design right, even if it isn't a blessed Best Practice, then paychecks happen.
b) 6-7. I've worked all around that spectrum, and found the happy medium to be 6-7. Anything over 8 is detrimental to shipping a product though.
c) Wherever they need to be for their project, organization and desired maintainability.
d) Not really. I try to put some up front thought into every non-throwaway design regardless of whether its high or low level because I'll end up with more maintainable code. However, sometimes other factors trump that.
We can program with only 1's, but if all you've got are zeros, you've got nothing.
|
|
|
|
|
a) It depends on my role. For mobile software I'm usually hovering around 7. In the corporation where I work (doing enterprise development) I try to stick around 8.
b) Honestly I think 7 and 8 are the most reasonable. At 9 or 10, while something to be aspired to, I don't really think is reasonable.
c) Anywhere from about 6 on up should probably be the way to go.
d) Definitely. If I'm just developing a website I would probably do the bare minimum to get it up and running and then fix it later. But, when writing mission critical software, then I try to go the extra mile because I don't want a bug coming back to haunt me for any reason.
|
|
|
|
|
I'm going to a fancy dress party – I selected a Darwin costume, naturally.
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
It'll be a long party, probably feel more like an endurance event
Sin tack
the any key okay
|
|
|
|
|
Are you going to bring your Beagle?
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
absolutely, need somewhere to stow the samples
Sin tack
the any key okay
|
|
|
|
|
Just wear the one that fits best.
Bastard Programmer from Hell
If you can't read my code, try converting it here[^]
|
|
|
|
|
The missus can go as Lady Godiva then.
|
|
|
|
|
I'd just go in some genes.
Ravings en masse^ |
---|
"The difference between genius and stupidity is that genius has its limits." - Albert Einstein | "If you are searching for perfection in others, then you seek disappointment. If you are seek perfection in yourself, then you will find failure." - Balboos HaGadol Mar 2010 |
|
|
|
|
|
DNA have yeer kilt laddie?
|
|
|
|
|
And, yet, the jokes fail to evolve...
|
|
|
|
|
Well done!
"Google Project Zero's Windows bug-hunter and fuzz-boffin Tavis Ormandy has given the world an insight into how he works so fast: he works on Linux, and with the release of a personal project on GitHub, others can too.
Ormandy's project is to port Windows DLLs to Linux for his vuln tests (“So that's how he works so fast!” Penguinistas around the world are saying).
Typically self-effacing, Ormandy made this simple announcement on Twitter......
Ormandy's reason for the project is to let loose fuzzing against Windows-based software, using Linux platforms.
“The intention is to allow scalable and efficient fuzzing of self-contained Windows libraries on Linux. Good candidates might be video codecs, decompression libraries, virus scanners, image decoders, and so on,” he writes.
Efficiency is the key, with Ormandy writing that on Windows, it's all too slow."
What's got a vast attack surface and runs on Linux? Windows Defender, of course • The Register[^]
|
|
|
|
|
If this ever becomes more than a research project, you can bet Microsoft will have something to say about it.
The difficult we do right away...
...the impossible takes slightly longer.
|
|
|
|
|
Richard Andrew x64 wrote: If this ever becomes more than a research project, you can bet Microsoft will have something to say about it.
You mean like what they've done over the last 20+ years with WINE?
/sarc
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, waging all things in the balance of reason?
Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful?
--Zachris Topelius
Training a telescope on one’s own belly button will only reveal lint. You like that? You go right on staring at it. I prefer looking at galaxies.
-- Sarah Hoyt
|
|
|
|
|
|
Samsung S8 'eye security' fooled by photo - BBC News[^]
I always remember a long time ago Mythbusters set out to test fingerprint authentication as found on anything from laptops to bank vaults. To prep for the feature they had a range of devices that offered fingerprint authentication all the way up to very expensive vaults and they also had a range of possible solutions to try. No doubt they were planning on starting with the more basic bits of kit and the most basic tools to circumvent and they'd get more and more sophisticated with their tools until the device was cracked. They would then move up to the next more secure device and repeat the process.
The simplest way they had to beat the system was a photocopy\printout of a fingerprint. The most complex involved a finger modelled in ballistic gel which matches the conductivity of human skin, and they had a mechanism to ensure the gel was also heated to body temperature. They basically tried to make the most realistic finger they could.
The whole bit was a damp squib though as the result was that the most basic of methods (a printout of a fingerprint) cracked the most advanced of the devices (the professional safe).
It's like the security industry is constantly looking for the next "big thing" and trying all these gimmicks and it's as if the gimmick is the most important thing....even more important than if the method actually works, and the end result is that things are getting less secure, not more.
|
|
|
|
|
F-ES Sitecore wrote: It's like the security industry is constantly looking for the next "big thing" and trying all these gimmicks and it's as if the gimmick is the most important thing....even more important than if the method actually works, and the end result is that things are getting less secure, not more. and not forget to say more expensive as they include the "latest" technologies
M.D.V.
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
Well, at least the battery didn't catch fire.
Are people really paying £800 for these?
98.4% of statistics are made up on the spot.
|
|
|
|
|
It cost no more than £650 - and the eye photo is free
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
|
Well, if it's down to 6.5 times what I paid for my 'phone, I have to admit it starts to sound a little tempting.
98.4% of statistics are made up on the spot.
|
|
|
|
|
Blimey - many times even my own fingerprint won't unlock my S6!
|
|
|
|
|
F-ES Sitecore wrote: It's like the security industry is constantly looking for the next "big thing" and trying all these gimmicks and it's as if the gimmick is the most important thing....even more important than if the method actually works, and the end result is that things are getting less secure, not m
I think a lot of that is probably implementation - they also employ the cheapest workers they can to produce the software, and I suspect that means they get their code from questions in QA...
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
OriginalGriff wrote: code from questions in QA
In that case you need no bother yourself with infrared images and contact lenses - just look at the phone with harassment...
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|