|
Yes, don't you? It's a 101 keyboard.
Of course, deletion can also be accomplished by selecting the offending code and typing something else.
|
|
|
|
|
If you have a numeric keypad on your keyboard, then there's prolly two delete keys.
Bastard Programmer from Hell
If you can't read my code, try converting it here[^]
|
|
|
|
|
It's probably been at least a dozen years (probably closer to 20) since I've done anything non-trivial with the numpad (some game that insisted on using it instead of simultaneous arrows for diagonal movement) except blow cruft out of it. I'd gladly discard it except that numpadless keyboards invariably do something stupid with the arrow and edit/navigation keys too and those I do touch type.
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
|
|
|
|
|
There is a real danger that bad code can be infectious - make sure that if you are staying, you can make the code professional before it turns you amateur.
|
|
|
|
|
Where are these places that people work where you are given time to re-factor average code? If I am given legacy code and it has broken, then the mantra is always 'just fix it'. I've yet to come across a place of work where they allow you to spend time re-factoring just because you don't think its up to scratch. Although if everyone coded half as well as people on CP claim to then we'd never have any issues. Right?
|
|
|
|
|
You are not given time to improve things - you have to take it.
(In practice, you build an improvement charge into your software estimates and over time the improving quality of the code pays back that investment)
|
|
|
|
|
|
It's called Shellshock, because names are trendy. "Just a spoonful of sugar helps the medicine go down"
Attention repost police: not a repost, it contains some more information on fixing it
|
|
|
|
|
Then why not for digital serfs [^] ?
« I had therefore to remove knowledge, in order to make room for belief » Immanuel Kant
|
|
|
|
|
The digital serf was a bit slow...
"I've seen more information on a frickin' sticky note!" - Dave Kreskowiak
|
|
|
|
|
Lucky that the instructors were able to save this lad: [^].
« I had therefore to remove knowledge, in order to make room for belief » Immanuel Kant
|
|
|
|
|
Resistance to the cloud is more emotional than technical, but gut reactions do matter. "To fear the worst oft cures the worse."
|
|
|
|
|
Let us remember, first of all, why we do code reviews. One of the most important goals of any professional software developer is to continually improve the quality of their work. Have those lessons been reviewed?
|
|
|
|
|
Quote: Millions of years ago, apes descended from the trees, evolved opposable thumbs and—eventually—turned into human beings.
Someone forgot to peer-review the author's intelligence factor...
|
|
|
|
|
I think it's reckless to use the word descended in this context.
|
|
|
|
|
Doesn't "opposable thumbs" indicate that you have two thumbs on the same hand?
|
|
|
|
|
No. It means you can fold your thumb over sideways on top of your palm. Try gripping various things either not using your thumb or only using it in the same curl method you can do with your other fingers. It's much harder.
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
|
|
|
|
|
ed welch wrote: Doesn't "opposable thumbs" indicate that you have two thumbs on the same hand? No, it means that they're only right some of the time.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
A patient dead on the table is a lesson.
|
|
|
|
|
I'm not going to your teaching hospital...
TTFN - Kent
|
|
|
|
|
Well, you may go; you may not come back.
|
|
|
|
|
Find me a programmer that is competent to review my code, and I'll be happy to do a code review. Otherwise, bugger-off.
Marc
|
|
|
|
|
The article states some reasons for code review, e.g.
ensure that at least one other person is familiar with your code.
help train new staff by exposing them to the code of more experienced developers. Does your statement mean that you are not at all interested in sharing your knowledge? Hm, strange, you've provided so many articles to CP, what a contradiction!
|
|
|
|
|
He didn't say he wouldn't, he said: "Give me a competent programmer"
That's very different
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.
|
|
|
|
|
Bernhard Hiller wrote: Does your statement mean that you are not at all interested in sharing your knowledge?
While I understand the reasons you quoted, they're sort of pie-in-the-sky wishful thinking. From my personal experiences, "familiarity with code" is really only achieved by working with the code and, more importantly, knowing the over-arching architectural decisions. I've found that I can show other people (even experienced devs) my code but, unless they are actively working with it, then its an "in one ear, out the other" experience. This stuff doesn't really stick. Certainly, that's my experience when someone shows me their code -- it only starts to stick when I have to work with it.
I've been down the path of helping to train new staff as well. The phrase "more experienced develoeprs" is a rabbit hole. Are the devs more experienced generally, for example in the framework or the language, or are they "merely" more experienced in the specific domain?
If the former, showing green devs complex code simply doesn't work. They need training, not show-and-tell. Ironically, green devs learn best by having people review their code, not my code, which results in a eye-glazing experience.
If the latter, then usually code is the worst way to learn about the business domain as it's often too narrow (and often biased) perspective of the business domain. New senior devs should be reading documentation, working with the product(s), and talking to both management and other devs about goals / issues. Another great technique for new senior devs is to participate in pair programming, that way they learn about how the architecture drives the code that supports the domain. A code review is far too disconnected from that process.
So, that's my hopefully more intelligent response to your very good question.
Marc
|
|
|
|