|
Figure C: "here are the programming languages that developers most want to work with "
Android? Arduino? Raspberry PI? iOS? Node.js?
Those are programming languages? I think somebody got confused.
For enterprises that are determined to remain relevant, the best way may be simply to get out of the way and let your developers build
I would say that's true at all scales, but then again, I have also seen the crap that developers build without any guidance, to put it politely. It's a rare developer that can actually produce something of quality on their own. Unfortunately, the same is true of project leads, managers, and most importantly, the client. Hence, it's a rare thing indeed to succeed at the concept "remain relevant."
Marc
|
|
|
|
|
Me think, "a veteran technology columnist" should not write such BS...
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
|
Dare I say it that the reason that corporations don't unleash developers on the latest tech is because it changes so fast that they won't complete anything before they want to jump onto the next shiny bandwagon. The average developers motto should really be "Look Squirrel!"
|
|
|
|
|
One of the many reasons developers cannot simply be "let loose" and develop what the enterprise needs, is because the developers do not know or even care what the enterprise needs.
Most want to create. And yes, create with the tools they want to work with and build the systems how they want. Unfortunately, you need much greater understanding of the organization before they will simply be capable of producing what the enterprise needs.
On the other hand, the enterprise managers should be the ones that understand what the enterprise needs.
A better fix would be improved communication between the devs and managers. If the devs want to build the system with different tools, the burden should be theirs to convince management of the benefits, and how they will mitigate risks.
Management is after all, the group funding these projects and responsible for the risk.
|
|
|
|
|
Paul M Watt wrote: One of the many reasons developers cannot simply be "let loose" and develop what
the enterprise needs, is because the developers do not know or even care what
the enterprise needs.
You are talking about a "coder". A developer should be able to analyze the information-flow.
Paul M Watt wrote: Unfortunately, you need much greater understanding of the organization before
they will simply be capable of producing what the enterprise needs.
It is preferred to not understand it; takes away bias. It is nigh impossible to make people challenge their assumptions, but rather easy to convince someone that does not know that it is beneficial to verify.
Paul M Watt wrote: On the other hand, the enterprise managers should be the ones that understand
what the enterprise needs.
That is a somewhat different field.
Paul M Watt wrote: If the devs want to build the system with different tools, the burden should be
theirs to convince management of the benefits, and how they will mitigate risks.
Ah, you can ask for a list of advantages and disadvantages, and what risks might be involved. The decision (and responsibility) is however for management 
Bastard Programmer from Hell 
If you can't read my code, try converting it here[^]
|
|
|
|
|
Eddy Vluggen wrote: You are talking about a "coder". A developer should be able to analyze the information-flow.
I mean developer in the broadest sense. It's what they spend their time focused on that I am referring to. Analyzing and making the product or tool better captures our interest.
Eddy Vluggen wrote: It is preferred to not understand it; takes away bias. It is nigh impossible to make people challenge their assumptions, but rather easy to convince someone that does not know that it is beneficial to verify.
I agree. Furthermore, many developers do not want to know. They are happy to have a place to hang their hat, and practice their trade. I have worked with many engineers with 20+ years of experience that are oblivious to how the company makes money. They simply want to create stuff.
Eddy Vluggen wrote: That is a somewhat different field.
How so?
Eddy Vluggen wrote: The decision (and responsibility) is however for management
Yes it is. He who holds the purse strings, makes the decisions.
|
|
|
|
|
Paul M Watt wrote: I mean developer in the broadest sense.
Like in "anything breathing that can write code" 
Paul M Watt wrote: They are happy to have a place to hang their hat, and practice their trade. I have worked with many engineers with 20+ years of experience that are oblivious to how the company makes money.
I do not need how they make money; what I need to know is what information you need to make your decisions - means asking you a lot of questions, since you are the expert on your company. And I will hit on every assumption you make, everything that is open to interpretation from a layman gets challenged. And all those points will be gathered into documentation, will be verifyable, and traceable.
Paul M Watt wrote: How so?
A manager is not a programmer; it would be rather hard to convince someone who does not understand the implications of his choice.
Paul M Watt wrote: Yes it is. He who holds the purse strings, makes the decisions.
And so the blind often do
Bastard Programmer from Hell
If you can't read my code, try converting it here[^]
|
|
|
|
|
University group reveals geo-inference attack threat that uses browser cache to reveal user location. "I will look for you, I will find you"
|
|
|
|
|
Following a four-month trial, a German court in Hamburg has ruled that the practice of blocking advertising is perfectly legitimate. "It is the spirit and not the form of law that keeps justice alive."
|
|
|
|
|
"determine his or her own Internet experience. It is living proof of the unalienable right of every user to enjoy online self-determination"
Way to alienate people, you stupid dick. Even I don't want to support you now, if that's the way you'll talk to me.
99% of the time, talking in hifalutin English makes you look stupider, and your propositions less attractive.
As his audience is "the general internet user", he should have spoken to them, not to impress his idiotic English teacher.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
You spelled "hifalutin" wrong. 
- I would love to change the world, but they won’t give me the source code.
|
|
|
|
|
hunh?[^]
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
It should have an apostrophe at the end. Collins dictionary is also wrong.
- I would love to change the world, but they won’t give me the source code.
|
|
|
|
|
Forogar wrote: It should have an apostrophe at the end.
No it shouldn't.
Forogar wrote: Collins dictionary is also wrong.
No it isn't.
I do so enjoy being positive.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
Nadella began as CEO in February 2014, and, after a little over a year, it’s too early to judge the results of his tenure. ... so, let's judge Satya Nadella
|
|
|
|
|
He's the CEO of Microsoft. He was being judged before he was even born.
Marc
|
|
|
|
|
NailO is a bundle of electronics crammed into a tiny package. It uses capacitive sensors—the same sort in smartphone screens—to register gestures. There’s also a battery, microcontroller, and a Bluetooth chip that lets NailO to any Bluetooth-enabled gadget. How do you switch batteries? Where do I put the penlite?
Bastard Programmer from Hell 
If you can't read my code, try converting it here[^]
|
|
|
|
|
"He got tired of fighting with his computer for the last several months," Lt. Jeff Strossner said. "He was having technology problems, so he took it out in the back alley and shot it." HAL? Does it hurt?
Bastard Programmer from Hell
If you can't read my code, try converting it here[^]
|
|
|
|
|
Earlier today, a new video of Windows 10 for Phones showing off some new features. The video shows off a new settings for developers – dubbed as “For Developers”. Does that come with leather interior and racing stripes?
|
|
|
|
|
Here is my list of heuristics and rules of thumb for software development that I have found useful over the years. "O this learning, what a thing it is!"
|
|
|
|
|
Yup, pretty much how I have always worked so gets my 5. 
|
|
|
|
|
Nice article. Short, to the point, and IMHO right on the money. +5 
/ravi
|
|
|
|
|
This is why software development is not a science. We seem to keep repeating these lessons every few months as if they are revelations. Seems like nobody actually pays attention.
Marc
|
|
|
|
|
Agreed. I waffled on this one a few times, as everything seemed ... like everyone should know them. But, I guess it just takes hitting the heads with yet another hammer. Or I'm just wasting time repeating it, and people will forget again in a few minutes.
Wait. What was I talking about again?
TTFN - Kent
|
|
|
|
|
Kent Sharkey wrote: Wait. What was I talking about again?
Squirrels![^]
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
