which technologies you really hate?
-
I have a check list to do so! 1. Calm down 2. Hit the 'Transfer call' button 3. Calm down 4. Enter number 5. Calm down 6. Put down the phone 7. Calm down
Skipper: We'll fix it. Alex: Fix it? How you gonna fix this? Skipper: Grit, spit and a whole lotta duct tape.
-
1. SharePoint 2. SharePoint 3. I almost forgot - SharePoint.
You're like me with Oracle. I used to have to program in that mess. I told a headhunter not to send me to any jobs that required Oracle programming. Where did he send me? To a place they sacrificed a goat every morning to the God Oracle. I called him up and said, "They do Oracle here, I told you I don't like Oracle. They want me to program Oracle here. Did I mention I don't like Oracle? Nothing but Oracle programming here. Did I mention they use Oracle here? (this goes on for at least five minutes)" His response, "They do Unix as well." "Only long enough to start Oracle!"
Psychosis at 10 Film at 11 Those who do not remember the past, are doomed to repeat it. Those who do not remember the past, cannot build upon it.
-
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.
Non-politically correct answer: Like that which feeds my family and pays the bills or shows potential to do so. All else is subject to hate. :)
-
If I quote CG "Java is like this Japanese soldier, who fought WWII in the jungle twenty years after the war was over". So Java may popup time to time, just to annoy the people, and is still supported from some organizations like Oracle for example, put it pretty much dropped from the technology main stream years ago.
There is only one Vera Farmiga and Salma Hayek is her prophet! Advertise here – minimum three posts per day are guaranteed.
-
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.
Surprised about XML. I find it easier to read (as a human) than equivalents (i.e json) so long as the XML format itself isn't tortured (i.e what SAP does to it). I mostly like the System.Xml.Linq namespace classes for dealing with it - particularly cool when building xml documents from object models. Speed and size can be issues, but TBH speed has never really been a problem for us and size is manageable (if still not as good as json) if you compress before transport. To each their own I guess. Web services - Again I have no problem with the MS implementation and tooling, and SOAP while it has some overhead, actually does things for you that you often have to build in yourself otherwise. I am Perfectly happy building and using .Net SOAP services in VS. However, I would probably put this on my list because *every* *single* php SOAP service we've ever been asked to use has had a badly formed WSDL which breaks the MS tooling, and trying to get PHP developers to acknowledge that I like pulling teeth. It always ends up being the WSDL and the php guy's fault, but they always insist it isn't. Agree about COM. It's had it's day, and while it has some good points, mostly it's a PITA. I can't believe WinRT is based on it. Makes me sad. I shall cry into my coffee. I would put iOS on this list. I know I'm like the only person on the planet that feels this way, but every time I use it I find it unintuitive, frustrating, ugly and somehow it feels 'old'. I always thought if I didn't have a WP I'd want an iPhone over Android, but having done some Xamarin development recently I think Android might actually be my preferred option. I also have a love/hate relationship with Xamarin, and particularly Xamarin Forms at the moment. The concept is awesome. The execution is filled with missing features, broken tooling, bugs, performance issues, and what looks like (though I haven't proved) poorly thought out implementation that isn't easily extended/replaced. WinRT - Ugh. Ugly API's. Missing API's. Poor exception logic, with poor reporting across language boundaries. Features missing (inheritance in public WinRT components) because... jscript. COM underneath. WTF. Ugh. Jscript. I'm not a web dev, and I don't like the web stack much so I'm biased anyway. The tools have also come along way since I last tried, so probably I'm just out of touch. However, personally, I don't like the language and have always found the tools awkward/lacking whenever I've tried to use it. Basically my initial experiences put me off so much I do e
-
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 thought I was the only one. I mean I'm a software engineer but I hate the phone, any phone, mobile phones included, especially smart phone. I'm forced to carry a beeper. I never figure out how to use my desk phone until may be a year or so into any new position.
-
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 phone". Every day cutting edge gadgets: "The phone". Every year new technology: "The phone". Every one is excited about new toy coming out: "The phone". Every technological news: "The phone". For the last 15+ years of innovation: "The phone". The future of automation: "The phone". Radio Shack is not selling anything else anymore except: "The phone". Arrggghhh!!! I hate "The phone".
-
Surprised about XML. I find it easier to read (as a human) than equivalents (i.e json) so long as the XML format itself isn't tortured (i.e what SAP does to it). I mostly like the System.Xml.Linq namespace classes for dealing with it - particularly cool when building xml documents from object models. Speed and size can be issues, but TBH speed has never really been a problem for us and size is manageable (if still not as good as json) if you compress before transport. To each their own I guess. Web services - Again I have no problem with the MS implementation and tooling, and SOAP while it has some overhead, actually does things for you that you often have to build in yourself otherwise. I am Perfectly happy building and using .Net SOAP services in VS. However, I would probably put this on my list because *every* *single* php SOAP service we've ever been asked to use has had a badly formed WSDL which breaks the MS tooling, and trying to get PHP developers to acknowledge that I like pulling teeth. It always ends up being the WSDL and the php guy's fault, but they always insist it isn't. Agree about COM. It's had it's day, and while it has some good points, mostly it's a PITA. I can't believe WinRT is based on it. Makes me sad. I shall cry into my coffee. I would put iOS on this list. I know I'm like the only person on the planet that feels this way, but every time I use it I find it unintuitive, frustrating, ugly and somehow it feels 'old'. I always thought if I didn't have a WP I'd want an iPhone over Android, but having done some Xamarin development recently I think Android might actually be my preferred option. I also have a love/hate relationship with Xamarin, and particularly Xamarin Forms at the moment. The concept is awesome. The execution is filled with missing features, broken tooling, bugs, performance issues, and what looks like (though I haven't proved) poorly thought out implementation that isn't easily extended/replaced. WinRT - Ugh. Ugly API's. Missing API's. Poor exception logic, with poor reporting across language boundaries. Features missing (inheritance in public WinRT components) because... jscript. COM underneath. WTF. Ugh. Jscript. I'm not a web dev, and I don't like the web stack much so I'm biased anyway. The tools have also come along way since I last tried, so probably I'm just out of touch. However, personally, I don't like the language and have always found the tools awkward/lacking whenever I've tried to use it. Basically my initial experiences put me off so much I do e
Wow, reading the other answers, so many good suggestions. Phone/smartphone, internet, PDF, regex. Yep, dislike all those on some level too. I also have to say I enjoyed computers much more before they became a social tool. Sitting alone in the basement in the dark hammering out code no one would ever see, that was fun. All this connected all the time, social, communication/chat rubbish has just ruined computers for introverted geeks like me. :laugh:
-
Thornik wrote:
just google what you need.
I don't have access to any site except MSDN. It took me 3 years to have access to CodeProject and StackOverflow. So I couldn't ask anything - but MSDN should provide ALL the documentation. If you describe me a tool in any aspect but you don't tell me what I'm supposed to do with it then it is useless, I will never use that tool anyway.
Geek code v 3.12 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--- r++>+++ y+++* Weapons extension: ma- k++ F+2 X
-
an example. MySql doesn't support milliseconds in their datetime objects... See here[^] However, when MySQL stores a value into a column of any temporal data type, it discards any fractional part and does not store it.
V.
(MQOTD rules and previous solutions):doh: You rather conveniently left-out the very next sentence. "MySQL 5.6.4 and up expands fractional seconds support for TIME, DATETIME, and TIMESTAMP values, with up to microseconds (6 digits) precision:" It seems apparent that the origin of this particular problem lies with the people controlling your working environment, rather than MySQL. This version of MySQL (5.6.4) was released over three years ago. (20 dec 2011)
-
1. SharePoint 2. SharePoint 3. I almost forgot - SharePoint.
-
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. :)
-
:doh: You rather conveniently left-out the very next sentence. "MySQL 5.6.4 and up expands fractional seconds support for TIME, DATETIME, and TIMESTAMP values, with up to microseconds (6 digits) precision:" It seems apparent that the origin of this particular problem lies with the people controlling your working environment, rather than MySQL. This version of MySQL (5.6.4) was released over three years ago. (20 dec 2011)
-
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.
- JavaScript. No explanation needed. 1) Social media APIs. The very idea that a social media company can up and decide at any time to change/deprecate/turn off APIs that are widely used all over the Web just makes my blood boil. This kind of thing happens with applications too, but on the Web it can hit you suddenly, there's no workaround, and usually poor documentation and communication about the change and little or nothing in the way of actual support. I'm starting to get the feeling that no matter who I work for, I'm really working for Twittter/FB/etc.
-
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.
Here is my list: XML - all that MS hype years ago that XML would take over the Cosmos - yes, OK! ASP.NET - still haven't found a use for it! (Besides the IDE wont run well on my old PC). MS Office ribbons - illogic incarnate! Touchscreen-style interfaces - yuk! Mobiles - those small screens do my head in! MS Windows post-XP: still waiting for something good ... Installing software on Linux - is this meant to be intuitively obvious?
