|
Spec must be implemented as capable by device. There is no need to implement a set of, for example, response flags that detail the state of the storage memory if the device does not have storage capability in the first place. It's enough just to stick them to the "all fine, nothing to see here" set of values.
The same goes for a lot of seldomly used features, like certain timeouts, watchdogs...
GCS d-- s-/++ a- C++++ U+++ P- L+@ E-- W++ N+ o+ K- w+++ O? M-- V? PS+ PE- Y+ PGP t+ 5? X R+++ tv-- b+(+++) DI+++ D++ G e++ h--- ++>+++ y+++* Weapons extension: ma- k++ F+2 X
|
|
|
|
|
AFAIK, a domain-specialist never gets trained in what a spec is; so it must be a developer who writes them.
Munchies_Matt wrote: I think it is because the spec writers want to make it complete, and because of their depth of knowledge, understand what they are thinking.
Where only a developer can be a spec-writer; otherwise you'll get a lot of data and facts that are irrelevant to the project.
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.
|
|
|
|
|
|
Munchies_Matt wrote: There are not written by developers. Specifications[^]
So you found one exception, and proclaim it the way things work.
Show me a single formal education where you learn wat version-control is and how to write technical and functional specs 
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.
|
|
|
|
|
WTF?
Look, specs like that are not written by developers?
USB spec?
RTCM?
They are written by engineers FFS!
|
|
|
|
|
Munchies_Matt wrote: Look, specs like that are not written by developers?
USB spec?
RTCM?
They are written by engineers FFS!
That's hardware. Most of this site is about software.
And yes, they do come together in a similar way, but that little fact remains - that they are developers. Not writers, not public servants, not linguistic advisors.
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.
|
|
|
|
|
Eddy Vluggen wrote: Most of this site is about software.
What, CP?
WTF has that got to do with it?
Eddy Vluggen wrote: That's hardware
WTF?
A USB spec has some electrical aspects to it but it is almost entirely about the communication protocol AFTER the line voltage has been negotiated!
As for 3GPP, if you even know what that is, or RTCM, they are radio transmission technologies with complicated functionality.
|
|
|
|
|
Munchies_Matt wrote: WTF has that got to do with it?
Means that if you talk of specs, then software-specs will be assumed, not hardware.
Munchies_Matt wrote: A USB spec has some electrical aspects to it but it is almost entirely about the communication protocol AFTER the line voltage has been negotiated!
Software; again, done by developers based on the interface that the hardware-engineers supply.
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.
|
|
|
|
|
You arent defining firmware as hardware are you?
|
|
|
|
|
Who needs specs in an agile environment?
Let's just start with 'int main(int argc, char **argv)' and take it from there as we learn what is needed. We can code it immediately, and the code will show how to solve the problem. Code will never be out of sync with the spec, because the code is the spec.
As long as you use reasonable variable and function names, you don't even need comments. Out-of-date comments are even more misleading than out-of-date specs, because you trust them much more, being so close to the code. We all know that documentation is unreliable and should never be trusted.
The only thing that matters is what is written down as code. The code is the terrain. Design, specs, comments or any other sort of writing are just poor maps of the terrain. Get yourself out in the terrain to see what it is really like. Be agile!
|
|
|
|
|
I thought you were joking for a moment.
OK, when you grow up and write some real software you will know what I mean.
|
|
|
|
|
I did my first programnming assignments at the University on 80 column punch cards.
|
|
|
|
|
SO if you have been in the game so long why havent you ever had to work with a big complex spec, something like USB for example, or the GSM spec?
|
|
|
|
|
I am very happy with good specs; I have read thousands of pages of ISO and ITU standards, some of which are excellently written. Especially for interface/protocol specs, I am very fond of specs based on state machines - they tend to make the spec terse, complete and unambiguous. (If you would like an example, pick up X.225, the OSI protocol stack Session layer - it is outdated now, but could serve as schoolbook example of a FSM based protocol spec.)
If you are still in doubt: In my first post in this thread, I was most certainly joking. Except that I think it is no laughing matter, it is rather sad how little the young crop of "agile" developers value specs, good designs and thorough problem analysis. It most certainly reduces the quality of the software we produce nowadays.
If you want well designed, robust software today, do not try to find it among those agile software broilers pouring out from the universities. Seach for those who know the problem domain. If you want a sound editor, search for studio people. Do you need document creation software, go to the publisihng business. Do you need software to keep track of your dog breeding, go to the farmers' organizations. Do you need a programmer's workbench, go to the open source community, that they know well and produce high quality software for. But not for movie editing, dog breeding, office automation or map construction.
For many youngsters today, agile makes you specless. You are free to take whatever next step you want, without asking anybody without telling anybody.
Agile doesn't have to be that way. But quite often, that's the way it turns out. Writing down anything else than code is something your boss forces you to (if he does!), and you do it after completing the code; you do not preapre and use it as an aid in the implementation phase. If you suggest anything in that direction, everybody under thirty (and a fair share of the older ones) give you that ugly look and snare "Waterfall!" at you.
|
|
|
|
|
Sarcasm never comes over well in text. 
|
|
|
|
|
In this scenario agility is a must, and a good endurance helps a lot, to run away from angry customers 
GCS d-- s-/++ a- C++++ U+++ P- L+@ E-- W++ N+ o+ K- w+++ O? M-- V? PS+ PE- Y+ PGP t+ 5? X R+++ tv-- b+(+++) DI+++ D++ G e++ h--- ++>+++ y+++* Weapons extension: ma- k++ F+2 X
|
|
|
|
|
Specifications?
Wait, are you from the land of fairies and unicorns where such a thing as specifications exists? 
My current specs are "this is sort of what we want, can you do that?"
"Sure", and then I just make something and hope for the best
Mostly, I steer the customer instead of the other way around.
|
|
|
|
|
Those are called 'requirements' normally and yes, I have worked with blank sheets of paper too.
I am talking about stuff like the USB spec.
|
|
|
|
|
The kind that describes how to use a third party system? 
Those seem to be imaginary even in the land of fairy tales 
|
|
|
|
|
|
Munchies_Matt wrote: And have you ever looked at code, or products that supposedly implement the spec, ...and just the basics of the spec implemented?
Where I work, we have it easier. There are no specs to begin with.
Latest Article - A Concise Overview of Threads
Learning to code with python is like learning to swim with those little arm floaties. It gives you undeserved confidence and will eventually drown you. - DangerBunny
Artificial intelligence is the only remedy for natural stupidity. - CDP1802
|
|
|
|
|
How many projects you could afford to keep on the same solution?
Some blogs say it's 15-20. But this would be too little for large projects.
If I have to keep separate solution for different groups of projects (for the same product)
Then managing the dependency dlls breakage would be a nightmare.
How this is usually handled?
Lets say I have a Common.dll that's being used by 30 projects.
This means, I would prefer to keep all the 30 projects under the same solution (this is a bad idea?)
(I had seen people copy the Common.dll project into their own solution just to ensure the build is going easy  , but these are freshers)
So I'm trying to heap the projects under single solution.
And to keep the build process easy, I'm thinking to:
1. un-check the projects that are not involved in current build, in solution build settings.
2. Unload project itself if it's a POC, tester or something completely not needed for current build.
Am I doing this right?
Starting to think people post kid pics in their profiles because that was the last time they were cute - Jeremy Falcon.
|
|
|
|
|
I have a solution with about 50 - 60 projects in it. I have never explored the maximum, if there is one at all beyond reasonable memory limitations.
The whole thing compiles to several executables, services and server components and many shared libraries for every tier/layer.
I have lived with several Zen masters - all of them were cats.
His last invention was an evil Lasagna. It didn't kill anyone, and it actually tasted pretty good.
|
|
|
|
|
CodeWraith wrote: I have a solution with about 50 - 60 projects in it.
|
|
|
|
|
I guess Nuget would be a solution as said by Sander Rossel?
Starting to think people post kid pics in their profiles because that was the last time they were cute - Jeremy Falcon.
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
