|
We have some fairly complex forms in our C# application.
Visual Studio 2015 runs out of memory just about every 15 minutes, and needs to be restarted. A real momentum killer. 
The difficult we do right away...
...the impossible takes slightly longer.
|
|
|
|
|
...half the day. Brings down my productivity by 50%
... such stuff as dreams are made on
|
|
|
|
|
...but I'm sure improves your sanity 60%.
I'm retired. There's a nap for that...
- Harvey
|
|
|
|
|
Currently working on a big software team(to our companies standards). With everyone working on the same software and many of the same files, merging becomes a horror. Many times you take a couple of hours to merge your code with the latest which can take a couple of hours, just to find out after the merge that many of those files you've just merged has been updated again.
This can sometimes take a day on its own... It is not suppose to be so difficult.
|
|
|
|
|
Merge often, reduces the pain. But it kind of requires that your teams have agreed on everyone doing so.
... such stuff as dreams are made on
|
|
|
|
|
I have a lot of trouble with installation of software that doesn't have its own installer. I can spend hours trying to understand what the product developers were thinking about when they wrote the stuff. A lot of software seems to expect you to understand the terminology and keywords of the product and breeze through installation knowing the answers to all the convoluted questions.
I'm retired. There's a nap for that...
- Harvey
|
|
|
|
|
Working on multiple projects simultaneously. 
___ ___ ___
|__ |_| |\ | | |_| \ /
__| | | | \| |__| | | /
|
|
|
|
|
Project Paperwork
Steve
_________________
I C(++) therefore I am
|
|
|
|
|
For those of us that don't have the luxury of only wearing one hat, having to break out of "code mode" to do SA or Cybersecurity (or whatever) work can really kill a flow.
"There are three kinds of lies: lies, damned lies and statistics."
- Benjamin Disraeli
|
|
|
|
|
I don't use Nuget nor .NET (luckily) and my team is made of a single other person with whom I have a very friendly relationship (to the point he was the only coworker I invited at my wedding, which had a small number of guests) and we often see eye to eye with regards to technology.
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
|
|
|
|
|
Worked with one guy what was supposedly an ".NET Consultant" and was our project manager. He would tell you something... and if you asked a question he'd just repeat the same thing. Ok "your instructions are to put data into the report" and he repeated the same thing again... NOW just tell me which out of the 10 reports you want data in? After he was already mad because I was asking for details. He might have known what he wanted done... was just terrible at giving details about it.
|
|
|
|
|
You have those and the other side who believe they alone can force design patterns, naming conventions and architecture, going as far as renaming your variables behind your back in the versioning system, so the program won't work anymore. 
The entire team tried to talk to him to which he replied: "You don't understand what I'm doing..." 
|
|
|
|
|
Set out on a "20 minute" train ride. Arrive 3 days later - crumpled, grubby, dazed, late and dispirited.
98.4% of statistics are made up on the spot.
|
|
|
|
|
As MS continuously brings out newer versions of Visual Studio, Windows, .Net, VB.net, C#.net, etc. in a greedy attempt to boost sales in a mature and relatively saturated market, they seem to have forgotten their power base programmers and developers that create the programs and applications then the end users actually buy. They seem to have forgotten that they make tools, not the programs and applications people actually want. Yes, I DO classify MS Office as a "tool".
Having to re-learn new language nuances, bugs and workarounds at an ever increasing pace takes up more time than the actual programming. 
And don't get me started on the abysmal quality of the Help documentation. 
Someone needs to explain to MS that "Planned Obsolescence" is the thing that nearly broke American carmakers and Detroit in the 70's, and is a very bad idea.
Happy to be near the end of my career....
|
|
|
|
|
we still use vs2008 (and nothing later)
|
|
|
|
|
I am sticking with VS2015 myself....
While I deplore men sexually harassing women, I am quite in favor of hot young girls sexually harassing me....
Old men need love too...
|
|
|
|
|
VS6...
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
|
|
|
|
|
I developed software to run inside AutoCAD, and interface with a half-dozen other company's programs files. From 2000 to about 2010 we could keep up... add a couple of features every year, upgrade the IDE every three years, add connections to new features in the interface programs. I spent as much time working around "that feature has been deprecated" or a shift from ASCII to Wide Character as I did actually writing the software. Then it got crazy... My last disk had ten different installs for ten different configurations of OS/AutoCAD Version with 64-bit version versus 32-bit. With the documentation we offered and the straightforward interface we never got calls about the software itself, just the installation for all the possible configurations. I still have a client running Windows 2000 and I've never been asked if there is a Windows 10 version.
|
|
|
|
|
You don't have to pay for them, just use the community edition. And if your biggest gripe is that it makes you learn newer techniques, then I'm wondering if you really are suited for a programming position at all?
Nevermind the guy who struggled to implement ASCII->"Wide character" taking almost as long as the entire project to convert it.
Seems like you "programmers" these days have an inability to adapt from what you were taught and tend to bitch about a tool or a library not giving you what you want / making it difficult than just doing your fcking job? wow
|
|
|
|
|
Member 13079230 wrote: And if your biggest gripe is that it makes you learn newer techniques
Newer is not "better", it's just different. I have been successfully "learning new techniques" and programming for a living for over 35 years. I wonder if you will last in the profession that long? I'll bet you're one of those guys who is working on creating a "new" language/tool/library right now.
The survey was about what kills my productivity the most. Your inability to understand my answer makes me question your communication skills and future as a programmer/developer/new hip term you consider yourself to be.
Do you work for Microsoft, or (shudder) Apple?
Those that focus on Edge cases (the Bleeding Edge) hardly ever get any meaningful work done....
|
|
|
|
|
Ed Aymami wrote: programmer/developer/new hip term
How about 'apper'? We could also invent a verb. To app something, like 'I have already apped that problem'.
Ed Aymami wrote: for a living for over 35 years
And then Member_99999999 comes along and finally tells you how it's done.
Ed Aymami wrote: Do you work for Microsoft, or (shudder) Apple?
Don't be cruel and destroy all his illusions at once.
I have lived with several Zen masters - all of them were cats.
|
|
|
|
|
"Apper" is a handy name... but also <Carriage Return>apper.
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
|
|
|
|
|
Ed Aymami wrote: a greedy attempt to boost sales
Greedy? Microsoft employs thousands of people and needs to *pay* them. A company is supposed to make money, that's how economies work.
What if your boss were to call you greedy for wanting a performance review and a raise?
The difficult we do right away...
...the impossible takes slightly longer.
|
|
|
|
|
Wasteful meetings that could be handled through a quick discussion or email, that sort of thing. It's not just the time of the meeting itself, it's the spin-down and spin-up time around the meeting.
|
|
|
|
|
Engineers are NOT good writers. Period.
Usually the problem is lack of documentation; it simply isn't there.
When it is, it is frequently very poorly organized, as seen from a user's point of view:
Sometimes so 'structured' in an over-academic sense that until you have all the developer's abstractions into your head, it is impossible to guess where the concrete detail is found.
Sometimes, the engineer spends lots of time & space on explaining the last, super-fancy features, skipping everything about the fundamental mechanisms.
Sometimes, the documentation writer comes from some other environment, assuming that all readers share the same background so he can limit himself to the changes, say from Windows Forms to WPF.
Or, a printed book of 870 pages, neatly organized into 17 well defined chapter subjects - yet the author takes for granted that when you look up something on page 672, you have understood and memorized every single detail in the preceeding 671 pages.
Or, for online documentation, you are in a maze of twisting little passages, all alike, following links from the API to the class of the argument to the constructor to the class of the constructor alternativ list to a specific constructor to the enum definition to ...
Of course there are search functions. But we have had years of "my hit list is bigger than your hit list", so while fourteen million hits is bound to give a recall of very close to 100%, the precision is a small fraction of a percent. Actually, filtering functions were better ten years ago than they are today, but hit lists are magnitudes larger.
As long as you work only with a limited set high-fashion tools that you see in every project every day, and you need not know how things work, only how to invoke them, you can learn by heart most that you need. The problem lies in those things you use rarely, and neither time nor money allows you to go to a two week training course, yet you need to undertand it thoroughly. Then you may spend so much time with books and online searching that you may end up thinking that the two week training course might have been a good idea anyway, because documentation by itself is useless...
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
