|
To be fair, sometimes they do add extra details... like
"I did not change anything."
|
|
|
|
|
|
Hell yeah.
McAfee is installed at work and we have had really weirdo things happening... everytime we do get a "not so logical" thing, the first we do is to deactivate it for an hour (the only thing we can do due to server policies) or check the second most common cause... the windows updates.
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: McAfee is installed at work
We have it here as well.
We use Inno Setup for our product installers. One day I was working on an install script and compiled it. I got a popup message from McAfee claiming a real-time scanning violation. Inno Setup closed up. I restarted it, and the source for my install script was gone, as were a number of the files included in the install. McAfee had terminated the Inno Setup compile process and deleted all of the files (including source code) that process had opened. I only lost an hour's work, but still.
My problem report to IT was... flammable.
Software Zen: delete this;
|
|
|
|
|
Gary Wheeler wrote: My problem report to IT was... flammable.
Yeah... been there done that too...
We had a new password policy in a firm I worked too, where 90% of the workers were with mid to long term projects mostly on the way. Suddenly we had to change password every 6 weeks. I wrote an email to our IT that got escalated to the CTO and I got a very CTO-answer explaining me how wrong I was and how insecure was our previous policy.
A guy got a project ended, went 4 weeks in vacation and when he came back his first day was to go to the company, grab som equipment and go to the airport for a project somewhere in the US west coast (almost 30 hours until he reached the hotel). He slept and on the first work day, connected the VPN in the hotel, checked the emails and went to the customer...
Once there, the laptop wouldn't let him log in. He called me to explain the problem and I was like "oh, oh" (but rubbing my hands in my interior).
I went to the company and started a discussion with the IT about it. I supposed it had to do with the password policy. With vacations and the trip he went over the 6 weeks, the first log in the US was with an offline valid user, once he connected the VPN the windows got the message "password expired" and after the reboot... bye bye. Once they confirmed on their own, what I was telling them from the very beginning the good dialog started.
- He can change it with the Ctrl+Alt+Supr menu
* No he can't, because he can't log in
- Then he should use the password recovery option in the website of the company
* No he can't, because it only works in VPN and he can't log in in windows
- But he can use the VPN in other computer
* No he can't, our VPN certificate is in encoded in C: and he can't log in in windows
- OK, I have reseted the validity of his user, that should solve the problem
* No, it won't, because the change is only valid once you connect to the VPN (and we already spoke about it)
...
Rinse and repeat with two additional "support levels", the final solution was to send another laptop per messenger. That was Thursday, Laptop was expected to come on monday. The guy had not expected "holidays" and could do tourism, the company got a really angry call from our customers and had to discount the not worked days, we got a new password policy for 6 months instead of 6 weeks and I got the most satisfactory "I told you" in my whole life.  
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.
|
|
|
|
|
lmoelleb wrote: I did not change anything
That statement is always a lie.
Software Zen: delete this;
|
|
|
|
|
honey the codewitch wrote: What's your least favorite part of coding?
Implementing that rarely used (used less than 10 percent of the time) feature, which takes a huge coding effort, and
bigger testing effort.
|
|
|
|
|
Sorry I have to somewhat contradict you, but I don't think your question has a proper answer between professionals. My view is that we do the work, and the whole work or we get out of this profession or we call ourselves hobbyists.
What would you say of a surgeon who says "I enjoy cutting, but stitching not so much"? The oft repeated lament "I hate documenting/commenting" is driving me nuts: what good is your work if you cannot explain to someone how to use it or if you explain it badly? Saying that you don't want to cover with tests all significant cases is like someone performing a CAT scan and stopping in the middle: probably the other half is also OK.
Speaking for myself, I like my profession and try to do it the best I can. I strive to document my code (although English is not my mother tongue), write unit tests and, in general, do all the drudgery tasks associated with programming. The fun is doing the whole lot.
Mircea
|
|
|
|
|
I wasn't necessarily speaking professionally. In fact, in my OP, that code is something I developed on my time.
Check out my IoT graphics library here:
https://honeythecodewitch.com/gfx
|
|
|
|
|
Sorry, but it doesn't matter if it is "professionally" or "your own".
I know it is a very popular view these days, but I learned to document first, before even writing a single line of code. And that includes having (insisting! when it comes from an outside request) the specifications for a project.
And then, and only then, start "coding", according to the existing specs and docs. And if you do this, properly, without using shortcuts, this will drastically cut down on any debugging/testing/troubleshooting afterwards.
If you don't do this, you are just a code monkey, hacking away at a keyboard and you will always run into problems, no matter what the project is. And that "running into problems" is the real part that takes away any fun and satisfaction on this kind of job. It is NOT the documentation. And no, the documentation is NOT in the code, not by a long shot...
|
|
|
|
|
None of that has anything to do with liking it or not.
I spend plenty of time on documentation.[^]
It doesn't mean I enjoy it, and I don't mind saying so.
I should add: Furthermore, everyone's got their own opinion on how things must be done, will argue it 'til they're blue in the face, and everyone that does things differently is a "code monkey". I'm too old for that nonsense. When I start reading it, my eyes glaze over. I developed a process and order that works for *me* and allows me to produce solid, maintainable work. And it does work. I'm paid quite well, and my clients are happy with what I produce. At the end of the day, that's what matters, not how I got there.
Check out my IoT graphics library here:
https://honeythecodewitch.com/gfx
modified 28-Aug-23 12:57pm.
|
|
|
|
|
In an ideal world, I should get a specification which fully documents what something is needed to do. I write it and send it back having tested as far as I can, then the business does extensive tests and the bugs get corrected before it gets released.
So we should only need to code and test to the requirements and then the specification is the documentation.
As I said, "In an ideal world, ...". 
|
|
|
|
|
StarNamer@work wrote: ...and then the specification is the documentation.
As I said, "In an ideal world, ..."
Well, I have issues with that on two counts:
- the specification only provides the "black box" description of the code, what gets in and what gets out. It doesn't say how to do it. It is up to you, the programmer to choose/devise the best algorithm, data structures to be used, limitations and compromises you had to make and so on; in brief, the nitty-gritty of the implementation.
- as you say, the world is not ideal and specifications are not complete so you have to make decisions during the implementation on how to solve those blank spots in the specification. You do it either by going back to the user, or by making informed choices but in the end all that accumulated knowledge has to be put somewhere by someone and I'd argue that you are in the best position to amend that specification and transform it into a manual.
Of course things can be different if you are part of a humongous organization and you are just a little cog doing your little bit for an enormous project. In that case there are probably many other people doing documentation, testing, integration, etc. and you just have to do (well) your bit of coding. However the OP was talking of design and contrasting it with documentation and testing, often seen as "lowly" activities. My point was that, in smaller projects, where you have certain freedom to design and implement stuff, there are no "lowly" tasks and everything has to be regarded as equally important.
I could go on, but I already feel that I'm ranting. Sorry...
Mircea
|
|
|
|
|
What I now do probably falls under your classification as:
Mircea Neacsu wrote: part of a humongous organization and you are just a little cog doing your little bit for an enormous project
Most of our business users are quite happy specifying UI changes, notifying legal requirements and otherwise just treating the whole distributed setup as a "black box". The IT team keeps track of how everything really works!
I'd question describing my role as "a little cog" since it's more a case that I get the issues no-one else has managed to solve. I do more support and fixing than actual development these days but have probably worked on all areas of our main in-house application.
However, the "humongous organization" is probably correct as the company was blocked from an acquisition a few years ago as it would have had too much market share in the UK; my boss used to describe it at trade fairs as "the largest UK company you've never heard of"!
|
|
|
|
|
StarNamer@work wrote: I'd question describing my role as "a little cog"
I didn't mean that disparagingly. Little cogs doing their work well in a humongous organization put the man on the moon. In my book, they are all heroes. And, yes, some of them were programmers[^].
Mircea
|
|
|
|
|
Ditto Mircea, I agree.
In my grad school computer lab, we had the proverbial toilet paper picture with "The job's not finished until the paperwork is done!", on the wall next to our Data General Eclipse mini-computer. Our mentor/professor meant it as we got graded from A-to-Z in preparation for the professional world of computer programming.
"A little time, a little trouble, your better day"
Badfinger
|
|
|
|
|
Mircea Neacsu wrote: I don't think your question has a proper answer between professionals
So you like everything about your job?
Including the meetings with management?
Very few people like everything about their job.
In fact, not many people really like their job at all.
As for the rest of your post, I come across very little code that's properly documented, my own code included.
I don't find it all that important and neither does my customer and it's never been an issue.
Same goes for automated tests.
The greatest bottleneck in my code is a piece that requires extensive UI and integration testing (of which a part can't even be tested because third party).
It's faster and easier to just manually run the code a few times and get that code in order so there's fewer chances of it breaking.
Having said that, I hate writing documentation because the moment you write it the software will have evolved and the documentation is outdated and no one will ever read it anyway and for that reason I never trust documentation.
I also really dislike writing tests.
The only tests I've seen never broke until they did because functionality changed.
Never have I prevented a bug with tests.
I use tests when writing complicated and easy to test logic, like parsers (but I rarely write those and when I do they're simple parsers).
|
|
|
|
|
Sander Rossel wrote: So you like everything about your job?
Including the meetings with management?
Yes, I lived an enchanted life  My boss for 20+ years was the owner of the company, an intelligent, nice person who called meetings only when needed and kept them short and to the object. Otherwise, I had my share of delayed flights, lost luggage, running into the occasional idiot, in short the usual unpleasantness of life, but that's not something I could blame on my profession.
Sander Rossel wrote: In fact, not many people really like their job at all.
I know. In fact I see it as one of the best paths to a miserable life. Hopefully, most programmers who hang out in their spare time at a coding site, do enjoy their profession. Otherwise I'm very, very sorry for them.
Now about documentation:
Sander Rossel wrote: I don't find it all that important and neither does my customer and it's never been an issue.
Really? I imagine you provide your customer with some type of manual or instructions. As for documenting the internals of your program, if other colleagues need to look at your code, I'm not sure they enjoy the experience. If you are a team of one, it might not be that important in your younger years or if you are writing throw-away code that is used only once and never revisited. If you are writing reusable code, docs matter.
Sander Rossel wrote: I also really dislike writing tests.
The only tests I've seen never broke until they did because functionality changed.
Never have I prevented a bug with tests.
I don't know what type of code you are writing. It might be your case, but in my world tests do matter. I do complicated math stuff and I want to make sure it works for all acceptable inputs.
Some of the code I wrote has been in use for 10-15 years and that's because of a combination of being well-documented and properly tested.
Mircea
|
|
|
|
|
Mircea Neacsu wrote: but that's not something I could blame on my profession
Part of the job, I guess.Mircea Neacsu wrote: Hopefully, most programmers who hang out in their spare time at a coding site, do enjoy their profession.
I do Mircea Neacsu wrote: Really? I imagine you provide your customer with some type of manual or instructions.
None whatsoever.
My code is custom made for every customer so they know exactly what they're getting.
I get an occassional call like "Sander, if I press this button will it do x or y?", but that happens maybe once a year.
Mostly because all buttons are pressed on a weekly basis so people know what they do.
I've written plenty of manuals in the past and I think none of them were ever read.
Even with a manual, it's easier for my customer to call me than it is to find and read the documentation.
At one time the customer even requested a help menu, accessible from an "info-button" at the top right of the form.
We documented the entire form and added the button.
The only one who pressed it was me when they called "what does this do?"
One time a customer told me "I didn't know what to expect, but I opened it and I just knew where to go because the software is so intuitive."Mircea Neacsu wrote: if other colleagues need to look at your code, I'm not sure they enjoy the experience.
I recently got a new junior employee and he had little trouble working through my code.
It's not that hard either, you POST a form and end up in the OnPost method and you can figure it out from there.
A few if-statements, a for-loop, some validations, save something to the database... Nothing too complicated.
I have the advantage that most of my code has a GUI, which means most of the funtionality has a visible component, which also makes debugging a bit easier (there's always a clear entry point, like a button click).
Some of my code is a hassle to work with, but I wouldn't even know how to begin to describe it.
Just set a breakpoint and walk through the code line by line, I guess.
That's really the only sure way to know what code does.
Reversed, I never read documentation either.
If I have to read lots of documentation just to understand what's going on, it's probably bad code and the documentation would be just as bad.
On that note, writing good documentation is a skill in and of its own and few people know how to do it well.
I sometimes make a diagram when I have more than a few applications that make up a product.Mircea Neacsu wrote: I don't know what type of code you are writing. It might be your case, but in my world tests do matter. I do complicated math stuff and I want to make sure it works for all acceptable inputs.
Mostly LOB applications.
I really don't need to test that a button click results in some entity being validated and saved to the database.
I manually tested it and it works.
Every update probably works too, unless you're a huge nitwit who not only broke simple existing code (which usually means deleting it), but also didn't test it.
Let's put it this way, I've worked on such applications for 14 years and it broke maybe once or twice (not to say I don't have issues in production, I do, but rarely something a unit test would catch).
On top of that, I've seen such badly unit tested code (like unit tests that asserted an exception was being thrown because a class wasn't properly constructed in unit tests!) that I've come to believe most people simply don't understand testing, like writing documentation, and ultimately ends up being a lot of wasted time.
Don't even get me started on coverage!
Having a minimum test coverage is like saying programmers should write x lines of code a day.
That's not to say I dismiss all unit testing and that I've never applied it myself, but all in all, it's mostly not worth it for me (I do have a few unit tested classes).
Seriously, I don't get the fuss about documentation and unit testing (or commenting code for that matter, which has all the same problems documentation has, but it's even harder).
I think it's applicable to only specific branches/use cases, like your math-heavy applications.
Someone, sometime, decided that documenting/unit testing was a best practice and everyone just went along with it (just like scrum  ).
Mircea Neacsu wrote: Some of the code I wrote has been in use for 10-15 years and that's because of a combination of being well-documented and properly tested.
I know some bad programmers who don't even know what unit testing is and who don't document a thing, and their code's been running for 20-30 years (yes, still VB6, sometimes even with a dBase database).
Those applications were recently ported to .NET 2.0 (because the programmer didn't know any better) and SQL Server.
Somehow that's possible even without documenting and unit testing (or proper programming knowledge)!
|
|
|
|
|
Sander Rossel wrote: Part of the job, I guess.
Price to be paid for travelling to 50+ countries on 6 continents with all travel expenses paid 
Sander Rossel wrote: Mostly LOB applications.
I really don't need to test that a button click results in some entity being validated and saved to the database.
I manually tested it and it works.
There is some difference in purpose and scale. In my case, the same software was/is used for data acquisition and visualization by over 5000 customers who connected 200+ types of devices. Besides, operating costs for some of the customers were so big that a single day lost was more than the cost of our software. If it wouldn't have worked, they would have thrown it overboard and I wouldn't have had the chance of a comfy retirement. 
Mircea
|
|
|
|
|
Mircea Neacsu wrote: travelling to 50+ countries on 6 continents
I'd absolutely hate that part of the job 
I hate visiting customers, save for two are even closer than my own office (6 and 7 km vs. 14 km).
I don't like working from home all the time either though, need to get out and socialize once in a while 
Mircea Neacsu wrote: There is some difference in purpose and scale
That's my point exactly.
In your original post you said: "The oft repeated lament "I hate documenting/commenting" is driving me nuts: what good is your work if you cannot explain to someone how to use it or if you explain it badly? Saying that you don't want to cover with tests all significant cases is like someone performing a CAT scan and stopping in the middle: probably the other half is also OK."
However, at my scale, it adds more work and complexity than it takes away.
Just like almost everything, whether you need documentation and unit tests "depends" on your use case.
Not having proper build and release pipelines is leaving the job half-done though 
|
|
|
|
|
Sander Rossel wrote: 'd absolutely hate that part of the job
I hate visiting customers, save for two are even closer than my own office (6 and 7 km vs. 14 km).
To each his own: me, I love(d) travelling. Now my bucket list is empty. I still like vacationing but it's not the same as when you go for work and get a chance to know people and see their real life. I guess I'm more of a traveler than a tourist.
Sander Rossel wrote: Not having proper build and release pipelines is leaving the job half-done though
Amen!
Mircea
|
|
|
|
|
There's a marked difference between not enjoying something and not doing it. Mind the gap.
Check out my IoT graphics library here:
https://honeythecodewitch.com/gfx
|
|
|
|
|
Documentation, as I am no good at writing clear instructions. Testing comes a close second, as I get bored after a few iterations.
|
|
|
|
|
Quote: Documentation, as I am no good at writing clear instructions
Now appart from Q/A where you simply reply with a link, I have a strong feeling, that you are writing very good instructions 
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
