|
Agreed. I think some folk are confusing counting floors, with counting ceilings 
|
|
|
|
|
Eddy Vluggen wrote: Go stand outside. That's 0 floors. You are at "level 0". Yes, build a floor, we'll call that one. Dig, and we'll call it -1. The latter is counting, but the first is merely a statement of what is if you go outside - 0 floors!
What about "terrace" buildings that are built on the side of a hill, having more than one ground level floor?
I'm retired. There's a nap for that...
- Harvey
|
|
|
|
|
H.Brydon wrote: having more than one ground level floor?
Go to the top of the building. Jump. Count ground floors on impact.
One impact, one ground floor.
Bastard Programmer from Hell 
If you can't read my code, try converting it here[^]
|
|
|
|
|
a floor is a floor. A floor is the walking surface of a room or vehicle.
if you have 2 floors is your list, I mean building!
How many items in your Building?
2 floors.
And so the first floor in your building is the [0] item, no, i mean [0] floor.
As such it is Ground Floor.
And the 2nd item in your building is the 1st Floor.
See, simple.
|
|
|
|
|
Indivara wrote: No it is the first floor!
Elder one is a data scientist.
The sh*t I complain about
It's like there ain't a cloud in the sky and it's raining out - Eminem
~! Firewall !~
|
|
|
|
|
In past lives, one was a C programmer, the other was a Fortran programmer. 
If you have an important point to make, don't try to be subtle or clever. Use a pile driver. Hit the point once. Then come back and hit it again. Then hit it a third time - a tremendous whack.
--Winston Churchill
|
|
|
|
|
I think I have spotted the problem here. The elder programs in Excel while the younger programs in C#
|
|
|
|
|
The problem is that many people associate the word "first" with the number "one" and think that the two concepts are the same when they are not, they are distinct concepts.
In your children's case; I suspect that both are correct.
|
|
|
|
|
He has clearly developed a healthy disdain for VB (but probably doesn't know it yet.) 
Marc
|
|
|
|
|
It gets weirder: Some countries have different way to count floors. In Russia, the ground floor is the first floor. So a building with 3 floors has floors 1 to 3. In Germany, the ground floor is called the ground floor and the second floor is called the first floor. So a three-floor building would have floors 0 (ground) to 2. At least, there's a word for "above-ground floor" which I use.
|
|
|
|
|
Useful, as it answers the real question: how many flights of stairs I have to climb? 0, 1, 2.
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
If you think 'goto' is evil, try writing an Assembly program without JMP. -- TNCaver
When I was six, there were no ones and zeroes - only zeroes. And not all of them worked. -- Ravi Bhavnani
|
|
|
|
|
It should be obvious - Array index (in most of the cases) starts normally from 0. That explain a lot!
|
|
|
|
|
I don't think this is about floors, look at the title again.
And, yes of course, you can not learn coding unless you were born programmer.
Zero floor approach is a good sign, the younger kid is the one of us!
|
|
|
|
|
In Italy gorund floor is 0, then there are first, second and so on.
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
If you think 'goto' is evil, try writing an Assembly program without JMP. -- TNCaver
When I was six, there were no ones and zeroes - only zeroes. And not all of them worked. -- Ravi Bhavnani
|
|
|
|
|
All y'all saying that ground floor = 0 are correct.
All y'all saying that ground floor = first are also correct.
It's just that in many countries, floors are identified by an index (0) whereas in the US (and a few other places I surmise) floors are identified with a label ("first").
Different UI concerns, that.
|
|
|
|
|
Younger is using a zero index array and will struggle with the fence-post errors in later life.
|
|
|
|
|
Don't you mean a Bjorn programmer?
|
|
|
|
|
I wrote some software that is used once per month to import data from over 50 sources (excel files, databases, and web sites), save it in a database, and generate a series of 37 panels (for lack of a better term) that show various types of graphs and data grids, and then generate power point slides so management can be briefed by the various department heads.
They have another guy doing a Qlikview "application", and importing the same data (except the web site stuff because Qlikview can't do that), and generating similar panels.
We both have the same issues - the excel files are mostly created by humans, which means anything that changes in the formatting or layout of the file could cause major issues during the import process.
For the last four months, there has been a string of major changes that affect both the importing, layout, and content of the panels. This is where it gets good.
Because of the way I've written the code (WPF desktop app using MVVM), I can generate a new chart/grid, or an alternative version of an existing one, in less than 10 minutes. I can write a new importer in less than 15 minutes (in most cases).
My app can create powerpoint slides with editable sections (as appropriate). Qlikview cannot export to powerpoint. At all. So after the panels are generated as JPGs, the customer has to create the powerpoint slide himself, and then copy/paste the jpg onto the empty slide, and add the desired edit boxes. I ask you - what good is automation software when it doesn't freakin automate anything?
I can also use a stored procedure to tailor data retrieval for the viewmodel so no post-processing is required. On average, Qlikview requires at least three load operations to simply massage the data to a usable form.
My app can be refactored and generate results in a fraction of the time the Qlikview app can. A final advantage is that my annual salary costs significantly less than the annual support contract, developer licenses, user licenses, and server licenses for QLikview.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
|
|
|
|
|
Prepare yourself for the other guy's big argument (which he'll use to try to prove that his way should be kept and that you're a useless amateur, compared to him}:
"Ah, but it's not maintainable, and we can't afford to use hack jobs"
The stupid fight dirty, because it's the only way they can win.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
Mark_Wallace wrote: "Ah, but it's not maintainable, and we can't afford to use hack jobs"
If it wasn't maintainable, I wouldn't be able to leave on time at the end of the work having long since addressed any refactoring that needs to be done, while he's still trying to adapt to the latest source data file change. We've already had that discussion, and it started with almost exactly the same phrase you used. My boss made actually laughed at the local Qlikview advocate when he said my code wasn't maintainable.
Then he asked about documentation, and I showed him fully indexed and TOC'd requirements document, design document, implemetation document, and even an end-user's guide (that became worthless when we all decided that the nature of the data required that I be the sole user because I could fix the stupid crap that happens all too frequently. Over 1500 pages of detailed word documents, and the code is fully documented and backup up by a general flow chart in Visio.
My app has been in use for about a year, and I've addressed most of the mundane crap that seems to happen (like not correctly specifying the cell formatting in an excel doc). There are other issues that software simply cannot address (renaming columns, sheets or even files). It's gotten to the point that the only time I need to go into the code is when a new importer is needed or a chart/grid needs to be changed.
All of that sounds pretty freakin maintainable to me.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
modified 21-Aug-16 10:17am.
|
|
|
|
|
John Simmons / outlaw programmer wrote: Over 1500 pages of detailed word documents
Wow.
Careful, others might start thinking you actually have the patience of a saint.
|
|
|
|
|
Oh come on, they're generated.
|
|
|
|
|
Hand written (typed).
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
|
|
|
|
|
Sorry, forgot the joke icon.
|
|
|
|
|
So you meant "written by a tool"?
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
