|
Ah, yes. The old outsource because you're not smart enough to understand the underlying problems.
|
|
|
|
|
Yup, I sent a "no" to my boss yesterday. Again.
If he wants me to produce "CSV files", I'm going to produce proper "CSV files", e.g. ones which Excel recognizes as "CSV" as it's the de facto Standard for "CSV".
He, of course, replied that I should use vertical bars rather than commas because the whack-jobs downstream are using a tool which can't read CSV! In fairness, Microsoft's BCP utility can't read CSV either, but these people are supposed to be developers. And so it goes around again.
Some uber-whack-job up above must have read a blog post about how good this tool is and dictated that everyone across the enterprise needs to stop using what works and switch to this one. piece of crap. Hey, it's expensive, it must be good! 
And, yeah, the same uber-whack-jobs up above have also dictated that everyone needs to use "Scrum" even though every word out of their mouths proves that they have not the first clue what "Scrum" is. 
|
|
|
|
|
You make the "value" of the delimiter an option; reading and writing.
It was only in wine that he laid down no limit for himself, but he did not allow himself to be confused by it.
― Confucian Analects: Rules of Confucius about his food
|
|
|
|
|
|
PIEBALDconsult wrote: e.g. ones which Excel recognizes as "CSV" as it's the de facto Standard for "CSV".
That can bring problems... I am in the CSV world at the moment too, and it is a pity because German Excel wants "," for decimal separation, but c++ wants "." for decimal separator.
Having a:
Line 1_1; Line 1_2;
2 empty
Line 3_1; Line 3_2; Line 3_3; Line 3_4;
Line 4_1; Line 4_2; Line 4_3; Line 4_4;
Line x_1; Line x_2; Line x_3; Line x_4;
Opening in Excel to edit something and saving it, then opening with another text editor then you have:
Line 1_1; Line 1_2;;;
;;;;
Line 3_1; Line 3_2; Line 3_3; Line 3_4;
Line 4_1; Line 4_2; Line 4_3; Line 4_4;
Line x_1; Line x_2; Line x_3; Line x_4; Note the additional ";" in lines 1 and 2
And yes... I know, but that's the csv I get from customers... First line is variable and can be less or more than the data part (at least data is a "rectangle")
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.
|
|
|
|
|
Nelek wrote: but that's the csv I get from customers
 Glad I'm not the only one! I have one customer's csv import that looks like this:
"1201,05-41-2100-AP,12033.32,07-01-2020,07-31-2020"
Yes, each line is encapsulated in double quotes not to mention the blank lines and subotals/totals spread throughout. This is what they give me, and if I can possibly make things work, I handle it...in this case checking each line for a 34 at the beginning and ending, except where matching pairs occur without a comma, etc. 
After 20 years of dealing with imports, nothing surprises me anymore! It has resulted in some highly customizable options bloat.
One gripe I have about working with .csv files is the fact that Excel will automatically strip leading 0s simply by opening the file, even without saving. 
"Go forth into the source" - Neal Morse
|
|
|
|
|
Bah! That's nothing. How about a "CSV" file which is actually multiple tables of data interleaved? Each line begins with the name of the table it belongs to.
Something like this:
Teacher,Name,Subject,Room
Student,Name,Grade
Class,Name,Teacher,Room,Limit,Enrollment
Teacher,John Smith,Logic,42
Student,Jane Doe,12
Student,John Doe,12
Class,Advanced Logic,John Smith,42,20,Jane Doe|John Doe
|
|
|
|
|
At my last job the vendor and I had to transfer data between two different databases. This was at the height of the XML solves everything craze. When my boss, who was also the company owner, came to us and said to use XML we both looked at him and said no, we've already solved this issue with CSV files which are far easier to read and write.
|
|
|
|
|
Best to do it without writing it to disk at all though, read from one database and write to the other.
CSV is evil. Particularly in the absence of a standard. I try to avoid it.
My boss was on a JSON kick for a while, he'd read a blog post. It seems that he is incapable saying "no".
|
|
|
|
|
Is there a solution to this? Seems this is the case everywhere (maybe almost!) and don't see getting it changed.
Think, it's just live with the reaction for saying No.
And the best option probably would be to provide best guesstimate and take whatever comes on the way as much possible.
|
|
|
|
|
I often work with people from other cultures (programmers, customers, etc) where NO is forbidden. It makes life more polite and unnecessarily difficult. Even if I ask something as simple as "Do you understand?" and the heads politely nod 'yes' regardless of whether they followed me or not. 
|
|
|
|
|
SteakhouseLuke wrote: I often work with people from other cultures (programmers, customers, etc) where NO is forbidden.
I thought the same thing when I read that a dev actually said no to someone.
Most places there is no possible way to say no. They want an estimate and you give them one.
Completely meaningless, but very polite. 
|
|
|
|
|
SteakhouseLuke wrote: I often work with people from other cultures
I've had that experience - it definitely requires learning how to phrase questions differently, like "tell me what you understand from all this?"
|
|
|
|
|
Working with the Japanese can be soooo frustrating. I built an entire solution based on their response only to find out it was completely wrong. We had to send an interpreter to Japan to get straight answers.
Never underestimate the power of human stupidity -
RAH
I'm old. I know stuff - JSOP
|
|
|
|
|
In English we have "The customer is always right."
In Japanese they say "The customer is God."
|
|
|
|
|
Marc Clifton wrote: The irony is that this project manager went from being a bull in a China shop to a mouse - no facilitation, no responses to our emails when we actually need some information from the client that he could "facilitate", in fact, no communication at all except an hour before the scheduled weekly meetings "Are you guys ready?"
Decades ago I worked with a QA lead who very much felt that he needed to have some visible authority and that he was constantly getting his hands tied behind his back. He stopped caring and only showed up to collect his regular paycheck. Then he was accused of "not being a team player".
I saw him a few years after he was laid off, and was making the claim that "[Company Name] put an end to my IT career". I'm pretty sure he did that himself. As much as I don't like office politics, you have to learn what the rules are, and play by them. Don't sulk for months until you get fired just because you're not getting things your way.
|
|
|
|
|
The more I worked in the field, the more I understood the wisdom of two year olds.
When I was green I was asked to move a deadline on a 3 month project, up a month. I said maybe. My mistake.
Since then I have not been afraid of "no."
I realized part of my job was to protect management from themselves. Not in the job description, but when the project fails, who gets blamed? It is my responsibility, because it's my behind if it gets behind.
Real programmers use butterflies
|
|
|
|
|
honey the codewitch wrote: I realized part of my job was to protect management from themselves.
Yeah, so often the sad truth. Especially when the manager explicitly says "my boss is breathing down MY neck."
Oi. Talk about roll reversal, which it should be the manager's job to protect you!
|
|
|
|
|
I agree. It was one of things I really didn't like about the field.
Real programmers use butterflies
|
|
|
|
|
Quote: ...I was asked to move a deadline on a 3 month project, up a month...
I've been asked that recently in a similar timeline.
I said "OK"
Then I said "Which bits do you want me to leave out?"
I got some funny looks at that point, and the "nothing should be left out" response.
I then wasted another 15 minutes of my life explaining that the work they required would take 4 months, so they could either have all of the work after 4 months or some of the work after 3 months.
Now they've got me in overly frequent, regular meetings to review how we are against plan. The irony that these meetings are eating into my available dev time is completely lost on them
|
|
|
|
|
And people wonder where Scott Adams gets his material. The man must have worked in development.
Real programmers use butterflies
|
|
|
|
|
That's when you tell them things have slipped a week because of all the time wasted in meetings.
"They have a consciousness, they have a life, they have a soul! Damn you! Let the rabbits wear glasses! Save our brothers! Can I get an amen?"
|
|
|
|
|
I ran my own schedule using scheduling software and told the (user) PM that they had their schedule and I would use mine. Of course, they could look at mine. I had projected finish dates. If there was a "due date", I made them take out "requirements" until my forecast matched their due date (year-end). And, no (I said), "more people" won't help after a certain point. I was never "popular", but never late.
It was only in wine that he laid down no limit for himself, but he did not allow himself to be confused by it.
― Confucian Analects: Rules of Confucius about his food
|
|
|
|
|
I had to jump in a project that was already way behind schedule. My first week there was almost only letting people explain me what it should be done and where we were. I tried to analyze what the previous guy was doing and then I called my boss, because repairing that mess would take me more time than starting over again. He let me do it.
2 weeks later, I was already moving the machine in semi-automatic. Then an appointment with the customer was done.
When they came the project manager was trying to explain things where I was internally hitting my head against the desk. Then the customer started asking for things and the project manager would open his mouth. At some moment I got tired and said... NO.
All quiet, staring at me...
Customer: Pardon? What do you mean?
Me: Because blah blah blah
Next day he was speaking with me using "Du" instead of "Sie" (the formal form in Germany) the other team members were  and asked me if he knew him from before...
ME: No, I met him yesterday, why?
They: Because the project manager had been working for him as extern for 4 or 5 years and was still being spoken with "Sie"
I suppose I got his respect exactly when I said "No" and then I gave him technical reasons to support my "No" some of them even protecting the machine or the ergonomy of the future operators of his company. I gave him even an alternative (that he payed extra, because was against was written in the contract)
So yes, learning when to say "No", being confident enough to say it and good enough to counter with objective arguments... is one of the worthiest thing that comes with experience
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.
|
|
|
|
|
Nelek wrote: So yes, learning when to say "No", being confident enough to say it and good enough to counter with objective arguments... is one of the worthiest thing that comes with experience
Very 
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
