|
I haven't seen that book, but MS was talking about those ideas back in the 1990's
And I've work with that methodology ever since. It works!
CQ de W5ALT
Walt Fair, Jr., P. E.
Comport Computing
Specializing in Technical Engineering Software
|
|
|
|
|
Walt Fair, Jr. wrote: I haven't seen that book, but MS was talking about those ideas back in the 1990's
And I've work with that methodology ever since. It works!
Very cool. And I believe that it would/does actually work.
Those few principles are very, very good and get to the core of what should really happen.
|
|
|
|
|
Buzz word laden hype. I just want to know what the users are trying to accomplish.
Maybe I'm just bitter. 
Common sense is admitting there is cause and effect and that you can exert some control over what you understand.
|
|
|
|
|
When you find out -tell the users.
Socialism is the Axe Body Spray of political ideologies: It never does what it claims to do, but people too young to know better keep buying it anyway. (Glenn Reynolds)
|
|
|
|
|
S Douglas wrote: Buzz word laden hype.
Wow, you really thought those few bullet points were buzz word laden hype?
That's fine. Maybe you have a lot of experience and you know how to get to the point on a project?
That's probably it. I notice that after 25 years of software dev / IT work, projects are so repetitive it can seem like everything is hype.
|
|
|
|
|
So many devs are not business focused.
Just look at the complaining we had here recently about being asked to dumb down their code.
Had a case recently where a dev was complaining about being taken off a task because it had been given to him in order to make senior engineer.
My response was 'take care of the product and the career takes care of itself'. ie, focus on the product and nothing else. Not how cood your C++ is, how many fancy, nerdy, features of a language you can use, but instead on how quickly you can push good product out the door.
|
|
|
|
|
Munchies_Matt wrote: So many devs are not business focused.
That is a very true sentence. Devs often become way too focused on tech and tech is meaningless by itself.
Munchies_Matt wrote: 'take care of the product and the career takes care of itself'
That's a good mantra to work by. 
|
|
|
|
|
My company once offered me a huge cash bonus, per delivered project, as an incentive to release products faster.
I refused, because I go to work to play around, get smarter, and make the clients happy.
Just pointing out that your monetary motivation might not works as well as you'd expect.
Also, there's something missing in your list:
*** every iteration you reduce the amount of code you need to maintain
If you work towards the simplest solution that is still economically viable, you'll stumble upon the core values of your sub-domain, sooner rather than later.
Once you find those, you can re-align your business practices and reduce the amount of people you need.
Of course, instead of firing anyone, you should branch out instead to a related sub-domain.
Diversify whenever you have nothing to loose, so you don't get blind-sighted by rising oligopolies in your sub-domain.
|
|
|
|
|
KBZX5000 wrote: Just pointing out that your monetary motivation might not works as well as you'd expect.
I know what you mean. It's really more about _ownership_ than it is money. I've developed my own projects that have never made any money but I'm 100% invested in them. Money was the easiest (and maybe funniest) way to explain it.
KBZX5000 wrote: *** every iteration you reduce the amount of code you need to maintain
I totally agree with that. Sometimes I say, "the best solution may include no code at all" and people think that is strange for a developer, but code is not a panacea -- and as you know it often causes more problems.
Reducing code is always a great idea.
|
|
|
|
|
There is separation on software projects because no project is the primary focus of most of the people involved in it. Project owners have their management or other jobs to do, users have their main jobs to do, even the UX and coders have other projects they are working on. You can't get all these people in the same room at the same time all day every day. But if you can get them together in the same room at the same time for an hour or two every day, or twice a week or so, I think the project would be much more likely to succeed.
If you think 'goto' is evil, try writing an Assembly program without JMP.
|
|
|
|
|
Key to success is QUALIFIED developers (not an indian "seniors" with 1 year of experience) + FULL ATTENTION TO FEEDBACK. Last one never ever considered seriously in every company. Every "top" thinks "he rules" and just f** any opinion he doesn't like. FIRE HIM, he works AGAINST the company!
Software is not made for developers - it made for USERS. But exactly users are who listened the last! WTF??
If your manager/support/dev doesn't read every single feedback - he lose important info. If he cannot understand what user needs, he is clown occupying wrong position. Every feedback should produce idea or feature, there is no "empty feedback"!
This is why MS rolling down - everybody there thinks they are smarter than users. And they think they can round the Earth in their direction. MS will be destroyed in 5 years, they are not players anymore.
|
|
|
|
|
Thornik wrote: Software is not made for developers - it made for USERS.
I agree 100%. It is obvious that this rule is ignored very often because I run into so much software which:
Does Not Work:
1 the way you (user) expects
2 have the functionality that you (user) needs
3 loses the data you typed on the screen 
4 will not let you move to the next section or form because some hidden (to user) element is not filled out, but is also not obvious
And so much more.
|
|
|
|
|
Does hold your horses mean to be stable?
"It is easy to decipher extraterrestrial signals after deciphering Javascript and VB6 themselves.", ISanti[ ^]
|
|
|
|
|
OK, keep taking the tablets...
|
|
|
|
|
glennPattonWork wrote: keep taking the tablets
Said God to Moses.
Socialism is the Axe Body Spray of political ideologies: It never does what it claims to do, but people too young to know better keep buying it anyway. (Glenn Reynolds)
|
|
|
|
|
:boomtish: Dang there isn't one! We need a boomtish emoji Chris!
|
|
|
|
|
No, it means you have a good freezer.
Bastard Programmer from Hell 
If you can't read my code, try converting it here[^]
"If you just follow the bacon Eddy, wherever it leads you, then you won't have to think about politics." -- Some Bell.
|
|
|
|
|
Not yet, but it probably will.
I seen a post on Facebook about this the other day, something along the lines of: "I can't believe I am nearly 30 and have only just realised that hold your horses means to be stable". The post had 100k+ comments of people saying "OMG, I can't believe I didn't know this until now either!".
This seems to be quite a common trend (from my observations), posts claiming that X means Y, and as we all (should) know by now, the internet people believe what the internet people are told... no questions asked.
Soon, if not already, half the internet will believe "hold your horses" means to be stable, and good luck trying to convince those people they are wrong. So it will naturally just become a fact that 'everyone' knows is correct.
Or maybe you could just create a counter-post and un-convince them of this 'fact', they are very easily swayed...
|
|
|
|
|
Didn't knew about the Facebook thing.
"It is easy to decipher extraterrestrial signals after deciphering Javascript and VB6 themselves.", ISanti[ ^]
|
|
|
|
|
It's a site where people keep a book of their faces, it's quite popular...
|
|
|
|
|
It means slow down as in pull on the reins or "Whoa!"
|
|
|
|
|
No, Ithink it means that you have very small horses , if you can hold them!
CQ de W5ALT
Walt Fair, Jr., P. E.
Comport Computing
Specializing in Technical Engineering Software
|
|
|
|
|
Yes, and the measure of how well you hold them is called instability.
|
|
|
|
|
State a trap with key communication (9)
State = Mess
a trap = a gin
key = g
Communication = messaging
We can’t stop here, this is bat country - Hunter S Thompson RIP
modified 9-Aug-18 8:58am.
|
|
|
|
|
TELEGRAPH?
Just a guess based on "key communication" and STATE == TELL, but I don't think it's right.
Sent from my Amstrad PC 1640
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
