which technologies you really hate?
-
Here is my list: 1. XML (Both human and computer have difficulties reading this crap. It's slow as dismembered turtle. Also the tools and accompanying technologies related to XML are crap too. Only Java use to have some dissent XML libraries, but Java is dead for good, so no much use of these.) 2. Web Services (Spawn of the devil. Working with this gives you a depression. .Net tools are not so bad. SOAP is a good protocol. But the entre thing is hit and miss situation. Definitely the result not worth the effort, except for some specific cases.) 3. COM (I have more than a decade long, love-hate relationship with COM. Very useful in some cases, but PITA most of the time. Really steep learning curve.) 4. MFC (Haven't evolved a bit(pun not intended) for the last 15 years.)
There is only one Vera Farmiga and Salma Hayek is her prophet! Advertise here – minimum three posts per day are guaranteed.
Systems Hungarian! :mad: Oh technology, sorry. :-O
Wrong is evil and must be defeated. - Jeff Ello
-
The phone on my desk - it is able to handle almost any kind of singe-/multi- conversation, but I almost unable to handle it... I'm also terrified of fax-machines, each of them...
Skipper: We'll fix it. Alex: Fix it? How you gonna fix this? Skipper: Grit, spit and a whole lotta duct tape.
I recoil in terror if my desk phone rings
-
Deyan Georgiev wrote:
but Java is dead for good
I don't know what planet you are coding on, but I assure you, Java is not dead.
Well, I really keep trying to kill it, but I'm only one man!
Life is like a s**t sandwich; the more bread you have, the less s**t you eat.
-
I recoil in terror if my desk phone rings
-
Java is a good language. I don't knock it. As with any language or technology, there are those who know how, and those that don't know how.
Java is a good language, that's true. But the language and it's structure is just the tip of the iceberg. The accompanying libraries and technologies are more important. And I've never been very happy with the Java related technologies.
There is only one Vera Farmiga and Salma Hayek is her prophet! Advertise here – minimum three posts per day are guaranteed.
-
I recoil in terror if my desk phone rings
The ringing isn't the problem, but when some-one asks me to transfer the call I'm starting to sweat...
Skipper: We'll fix it. Alex: Fix it? How you gonna fix this? Skipper: Grit, spit and a whole lotta duct tape.
-
Here is my list: 1. XML (Both human and computer have difficulties reading this crap. It's slow as dismembered turtle. Also the tools and accompanying technologies related to XML are crap too. Only Java use to have some dissent XML libraries, but Java is dead for good, so no much use of these.) 2. Web Services (Spawn of the devil. Working with this gives you a depression. .Net tools are not so bad. SOAP is a good protocol. But the entre thing is hit and miss situation. Definitely the result not worth the effort, except for some specific cases.) 3. COM (I have more than a decade long, love-hate relationship with COM. Very useful in some cases, but PITA most of the time. Really steep learning curve.) 4. MFC (Haven't evolved a bit(pun not intended) for the last 15 years.)
There is only one Vera Farmiga and Salma Hayek is her prophet! Advertise here – minimum three posts per day are guaranteed.
-
The ringing isn't the problem, but when some-one asks me to transfer the call I'm starting to sweat...
Skipper: We'll fix it. Alex: Fix it? How you gonna fix this? Skipper: Grit, spit and a whole lotta duct tape.
I just pretend to drop the handset. Transferring calls is meddling in the affairs of wizards
-
java. It's terrible. MySQL. It's terrible (which is strange considering it is from Oracle) XML is, more or less OK although this does depend on the need. Here we work with CSV, ASCII, xls and FITS files all with their good and bad and worse formats, so here it's not technology itself, but rather how they use it. Linux. Some swear by it, I hate it. openoffice/libreoffice. :doh: open office is probably all right, but libre office? :wtf: iTunes. They should execute the humans involved in this piece of cr*p. Most technologies are OK depending on how you use them.
V.
(MQOTD rules and previous solutions)V. wrote:
Linux. Some swear by it, I hate it
You just have to use it enough to get used to it.... then the flexibility of it becomes quickly apparent (and neat).
V. wrote:
iTunes. They should execute the humans involved in this piece of cr*p.
I hate this piece of crap.... and Apple...
-
Here is my list: 1. XML (Both human and computer have difficulties reading this crap. It's slow as dismembered turtle. Also the tools and accompanying technologies related to XML are crap too. Only Java use to have some dissent XML libraries, but Java is dead for good, so no much use of these.) 2. Web Services (Spawn of the devil. Working with this gives you a depression. .Net tools are not so bad. SOAP is a good protocol. But the entre thing is hit and miss situation. Definitely the result not worth the effort, except for some specific cases.) 3. COM (I have more than a decade long, love-hate relationship with COM. Very useful in some cases, but PITA most of the time. Really steep learning curve.) 4. MFC (Haven't evolved a bit(pun not intended) for the last 15 years.)
There is only one Vera Farmiga and Salma Hayek is her prophet! Advertise here – minimum three posts per day are guaranteed.
I'm too busy having a life to actually hate a piece of software. Although, if I were to say something off the top of my head I'd imagine most things you can find on CNET are a pile of dung.
Jeremy Falcon
-
Java is a good language, that's true. But the language and it's structure is just the tip of the iceberg. The accompanying libraries and technologies are more important. And I've never been very happy with the Java related technologies.
There is only one Vera Farmiga and Salma Hayek is her prophet! Advertise here – minimum three posts per day are guaranteed.
I make my living with C#, and I complain about it everyday. It is anything but perfect, but it is better than stone tablets and post-it notes. :)
-
The ringing isn't the problem, but when some-one asks me to transfer the call I'm starting to sweat...
Skipper: We'll fix it. Alex: Fix it? How you gonna fix this? Skipper: Grit, spit and a whole lotta duct tape.
I had a person call my phone at my job (once). I really don't know why I have a phone. I write code... I don't talk to people unless it is about the code... why do I have a phone? This particular call was from an unrecognized number. I was thinking maybe it is important (this was a new job and I wasn't sure if I was expected to talk on the phone or not - it wasn't in the job description, but I wanted to do my best!) Anyway, it was an irate customer. She kept stating she was very dissatisfied (like I could comp her bill or get someone to fix her issue). I told her she had the wrong number and I was a software developer. She insisted this was the number to call. I repeated it was not (but tried to be polite) and directed her to the customer support number on our webpage. Again, she said she had called it numerous times and was very dissatisfied. She demanded to be transferred to a VP! I didn't know any VPs at the time, and I surely didn't know how to transfer a call. And I had no idea which VP could possibly help a very dissatisfied customer who had not yet explained her problem. Not being one to hang up I started to panic, sweat, and then I grabbed my boss. I handed him the phone and watched the whole thing play out again. Luckily, he knew how to transfer her to the customer support number on the webpage (where she had previously been very dissatisfied). Then he looked at me with large exasperated eyes and directed me to NEVER ANSWER THE PHONE AGAIN! I said ok, because, it really isn't in my job description anyway.
-
Here is my list: 1. XML (Both human and computer have difficulties reading this crap. It's slow as dismembered turtle. Also the tools and accompanying technologies related to XML are crap too. Only Java use to have some dissent XML libraries, but Java is dead for good, so no much use of these.) 2. Web Services (Spawn of the devil. Working with this gives you a depression. .Net tools are not so bad. SOAP is a good protocol. But the entre thing is hit and miss situation. Definitely the result not worth the effort, except for some specific cases.) 3. COM (I have more than a decade long, love-hate relationship with COM. Very useful in some cases, but PITA most of the time. Really steep learning curve.) 4. MFC (Haven't evolved a bit(pun not intended) for the last 15 years.)
There is only one Vera Farmiga and Salma Hayek is her prophet! Advertise here – minimum three posts per day are guaranteed.
For a list of all the ways technology has failed to improve the quality of life, please press 3. --Alice Kahn
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 had a person call my phone at my job (once). I really don't know why I have a phone. I write code... I don't talk to people unless it is about the code... why do I have a phone? This particular call was from an unrecognized number. I was thinking maybe it is important (this was a new job and I wasn't sure if I was expected to talk on the phone or not - it wasn't in the job description, but I wanted to do my best!) Anyway, it was an irate customer. She kept stating she was very dissatisfied (like I could comp her bill or get someone to fix her issue). I told her she had the wrong number and I was a software developer. She insisted this was the number to call. I repeated it was not (but tried to be polite) and directed her to the customer support number on our webpage. Again, she said she had called it numerous times and was very dissatisfied. She demanded to be transferred to a VP! I didn't know any VPs at the time, and I surely didn't know how to transfer a call. And I had no idea which VP could possibly help a very dissatisfied customer who had not yet explained her problem. Not being one to hang up I started to panic, sweat, and then I grabbed my boss. I handed him the phone and watched the whole thing play out again. Luckily, he knew how to transfer her to the customer support number on the webpage (where she had previously been very dissatisfied). Then he looked at me with large exasperated eyes and directed me to NEVER ANSWER THE PHONE AGAIN! I said ok, because, it really isn't in my job description anyway.
:laugh:
Skipper: We'll fix it. Alex: Fix it? How you gonna fix this? Skipper: Grit, spit and a whole lotta duct tape.
-
Here is my list: 1. XML (Both human and computer have difficulties reading this crap. It's slow as dismembered turtle. Also the tools and accompanying technologies related to XML are crap too. Only Java use to have some dissent XML libraries, but Java is dead for good, so no much use of these.) 2. Web Services (Spawn of the devil. Working with this gives you a depression. .Net tools are not so bad. SOAP is a good protocol. But the entre thing is hit and miss situation. Definitely the result not worth the effort, except for some specific cases.) 3. COM (I have more than a decade long, love-hate relationship with COM. Very useful in some cases, but PITA most of the time. Really steep learning curve.) 4. MFC (Haven't evolved a bit(pun not intended) for the last 15 years.)
There is only one Vera Farmiga and Salma Hayek is her prophet! Advertise here – minimum three posts per day are guaranteed.
- PDF - It is just such a terrible mess internally 2) Regex - this hurts my poor tiny brain
-
Here is my list: 1. XML (Both human and computer have difficulties reading this crap. It's slow as dismembered turtle. Also the tools and accompanying technologies related to XML are crap too. Only Java use to have some dissent XML libraries, but Java is dead for good, so no much use of these.) 2. Web Services (Spawn of the devil. Working with this gives you a depression. .Net tools are not so bad. SOAP is a good protocol. But the entre thing is hit and miss situation. Definitely the result not worth the effort, except for some specific cases.) 3. COM (I have more than a decade long, love-hate relationship with COM. Very useful in some cases, but PITA most of the time. Really steep learning curve.) 4. MFC (Haven't evolved a bit(pun not intended) for the last 15 years.)
There is only one Vera Farmiga and Salma Hayek is her prophet! Advertise here – minimum three posts per day are guaranteed.
1. SharePoint 2. SharePoint 3. I almost forgot - SharePoint.
-
java. It's terrible. MySQL. It's terrible (which is strange considering it is from Oracle) XML is, more or less OK although this does depend on the need. Here we work with CSV, ASCII, xls and FITS files all with their good and bad and worse formats, so here it's not technology itself, but rather how they use it. Linux. Some swear by it, I hate it. openoffice/libreoffice. :doh: open office is probably all right, but libre office? :wtf: iTunes. They should execute the humans involved in this piece of cr*p. Most technologies are OK depending on how you use them.
V.
(MQOTD rules and previous solutions)V. wrote:
Linux. Some swear by it, I hate it some swear at it.
FTFY ;)
V. wrote:
iTunes. They should execute the humans involved in this piece of cr*p.
Death is too good for them! :mad:
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
-
- PDF - It is just such a terrible mess internally 2) Regex - this hurts my poor tiny brain
-
Here is my list: 1. XML (Both human and computer have difficulties reading this crap. It's slow as dismembered turtle. Also the tools and accompanying technologies related to XML are crap too. Only Java use to have some dissent XML libraries, but Java is dead for good, so no much use of these.) 2. Web Services (Spawn of the devil. Working with this gives you a depression. .Net tools are not so bad. SOAP is a good protocol. But the entre thing is hit and miss situation. Definitely the result not worth the effort, except for some specific cases.) 3. COM (I have more than a decade long, love-hate relationship with COM. Very useful in some cases, but PITA most of the time. Really steep learning curve.) 4. MFC (Haven't evolved a bit(pun not intended) for the last 15 years.)
There is only one Vera Farmiga and Salma Hayek is her prophet! Advertise here – minimum three posts per day are guaranteed.
Deyan Georgiev wrote:
XML
THat gets my vote. Its useless. Utter junk. Its no better than an ini file, and has had so much said about it, and yet it has delivered so little.
Deyan Georgiev wrote:
COM
What was the point of COM? Replace dlls with a dll? Utter garbage.
Deyan Georgiev wrote:
. MFC
Here I disagree. It is very usefull, still, and the fact it hasn't changed means it was perfect as it was. :)
Sign a petition calling for the boycott of Israel until it returns to its legal 1967 borders.
-
java. It's terrible. MySQL. It's terrible (which is strange considering it is from Oracle) XML is, more or less OK although this does depend on the need. Here we work with CSV, ASCII, xls and FITS files all with their good and bad and worse formats, so here it's not technology itself, but rather how they use it. Linux. Some swear by it, I hate it. openoffice/libreoffice. :doh: open office is probably all right, but libre office? :wtf: iTunes. They should execute the humans involved in this piece of cr*p. Most technologies are OK depending on how you use them.
V.
(MQOTD rules and previous solutions)V. wrote:
Linux
Is it a 'technology'? Its just an OS, and a very usable one too. Unlike Windows, you can actually do what you want with it. XML is a load of cack though, truly.
Sign a petition calling for the boycott of Israel until it returns to its legal 1967 borders.
