|
nbize wrote: That's one of the worse example you could have come up with "Worst". And though many eyes help in spelling, as in bugfixing, it does not work pre-emptive. My apologies; but it is not unnatural to share code; the amount of open source shows that. It also hits another point; most businesses do not want us to share code in that fashion.
nbize wrote: There is no one-man show in success. No cheap one-liners, please. This one hinges on your definition of "success".
Bastard Programmer from Hell
If you can't read my code, try converting it here[^]
|
|
|
|
|
nbize wrote: What my article simply states is that when you write things that others will see, you will be more careful than when writing code that noone will see.
Your article does not state or imply that. If you had used these quoted words in your article in some manner I probably wouldn't have taken issue with it, but you would have had to restructure much of the rest of it for clarity around this new usage of 'solo coder,' and 'writing for others.' Without such words in it, your article is BS clickbait. You have written much better on previous topics, and I hope you get back to writing quality entries, although most programming subjects have already been hacked to death by bloggers somewhere.
I have said my peace. Thank you, and happy coding!
David
|
|
|
|
|
Well my whole 3rd paragraph was about that... But anyways you're not the only one pointing out that that message didn't come out right so I'll take some time to edit my post and make things clearer.
|
|
|
|
|
I look forward to seeing the revision, and am upvoting your response because it improved my estimation of you.
Best wishes,
David
|
|
|
|
|
I've edited the article. Hopefully it gives more precision about the parts that were misunderstood.
I'll see if I can include some sort of revision viewer in the future for those types of edits.
Cheers
|
|
|
|
|
You are still fighting a losing battle, because you say that I am 'doing it wrong.' The code to my main project will never be put forth for you, or others, to review. Yet it is as high quality as the code in any of my articles because I know that taking shortcuts only hurts me in the end. Your picture is still too black and white. But it is better than it was.
Best wishes,
David
|
|
|
|
|
In the end of the article, I precise what I meant by doing it wrong: "I am using the terms “doing it wrong” because there is so much more to gain from working on code as a group of individuals than as a solo dev". This does not mean that your code is bad. But just try this experiment: take any part of your main project code, post it on a dev forum and ask for feedback on what could be improved. I'd be surprised if everyone told you that everything was perfect and that you would not learn from others.
I'm not fighting a battle here. It's very hard to stay opiniated without appearing judgmental, and I might still need to change some phrasing or words so that my message is not misunderstood. And it's true that nothing is black and white, but I'd rather have sharp corners hoping that maybe one of my readers will have the desire to start asking for some feedback, to get some code review tool for his team, to be more open about his coding decisions, etc.
I'll take more time after work to get back on the article again and see if anything can be improved so that it is clearer.
modified 25-Nov-14 17:18pm.
|
|
|
|
|
Nicolas wrote: code that has been entirely designed and produced by a single person, code which has never been seen or reviewed by others peers, code that has been produced in the dark is always a code smell. This is too offensive and totally wrong conclusion and yet you're trying to persuade CP members. Most of CP articles are written with individual members and you are saying each members article codes are code smelled. What a conclusion ! Man there are lot of codes which always bring pain in the ass and fragile and yet developed and maintained by many devs.
As @Pete-OHanlon says you are not winning the war here.
Wonde Tadesse
|
|
|
|
|
You are misreading me. Aren't CP articles "seen / reviewed / commented" by others?
Just like any open source work done by solo guys, any article / code that ends up in the open for others to see is what I call code "in the light" and is praised in my article.
|
|
|
|
|
Yes it is. Anyone can comment the code in the comment section. If the code has defect it's also addressed. But don't expect every article to be commented. You can see mine. If you want too. And you can see my github as well. "This seems an advert" but it's an example what I gave you.
Wonde Tadesse
|
|
|
|
|
I do not like to use 'dark' words - but a few come to my mind reading these absolute nonsense...
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
|
Starting in January 2015, Google’s Chrome browser will block all old-school Netscape Plug-In API (NPAPI) plugins. This doesn’t come as a huge surprise, given that Google started its efforts to remove NPAPI plugins more than a year ago. There's another spike in Silverlight
|
|
|
|
|
From techcrunch.com: ...Silverlight still remains popular with 11% of Chrome users launching it at least once per month. What I want to know is how does Google know this? Does Chrome phone home every time a plug-in is launched?
Jeremy Falcon
|
|
|
|
|
There is a user setting for "Automatically send usage statistics and crash reports" I suspect they get a lot of data from that.
|
|
|
|
|
I thought that was for when it crashed, and isn't it disabled by default? If that is the metric the stat is based on, then for all we really know the percentage could be higher or lower than 11%. Then again, this is Google, so I'm sure they know I'm typing this right now. If you don't hear from me in a week, call for help.
Jeremy Falcon
|
|
|
|
|
How do you know they haven't prepared this reply and sent it on my behalf
|
|
|
|
|
Because Google would use a period or question mark to end a sentence.
Jeremy Falcon
|
|
|
|
|
ctart?
I think you need to start using Spell Check!
What do you get when you cross a joke with a rhetorical question?
---
The metaphorical solid rear-end expulsions have impacted the metaphorical motorized bladed rotating air movement mechanism.
|
|
|
|
|
Google is more and more "fencing its empire" ...
Press F1 for help or google it.
Greetings from Germany
|
|
|
|
|
To be fair, it may be the only way to improve security in the browser.
"If you don't fail at least 90 percent of the time, you're not aiming high enough."
Alan Kay.
|
|
|
|
|
Smoking will not only damage your health but also your computer, as e-cigarettes manufactured in China are reportedly being used to spread malicious software through the USB connection used to charge the device. Those things are bad for you, you know
|
|
|
|
|
Why would you plug one into a computer? Plenty of other USB ports available.
|
|
|
|
|
Because the PSU in your PC is almost certainly more efficient than the ones in standalone wallwarts.
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
|
|
|
|
|
It's just as well those projects to deliver networking through the same socket as mains electricity a few years ago never took off, or we'd never be able to charge anything safely.
"If you don't fail at least 90 percent of the time, you're not aiming high enough."
Alan Kay.
|
|
|
|
|
Rob Grainger wrote: we'd never be able to charge anything safely.
what about http://lifehacker.com/five-best-external-battery-packs-509802431[^]?
That way you might only check for safty once, then use it as "firewall"
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.
|
|
|
|