IT/Software career thread: Invert binary trees for dollars.
- Thread starter Traak
- Start date
-
Guest, it's time once again for the massively important and exciting FoH Asshat Tournament!
Go here and give us your nominations!Who's been the biggest Asshat in the last year? Give us your worst ones!
Vinen
God is dead
- 2,791
- 497
Fuck who knows. This rumor looks more credible then the last but VMware being the mix (company I work for) definitely throws the entire EMC/Dell merger into what the fuck realm.
I'd love to see who will help them raise the capitol for this.
Noodleface
A Mod Real Quick
- 38,371
- 16,276
I wouldn't be surprised if Dell was only buying VNX or something, but that is conjecture on my part.
Warrian
╰⋃╯ლ(´ڡ`ლ)
- 141
- 29
Vinen
God is dead
- 2,791
- 497
Now if the journalists can agree on a price per/share they are ripping out of their ass :3
I've seen at least 5 of them today LOL. Will be interesting to see the clusterfuckery which ensues.
Noodleface
A Mod Real Quick
- 38,371
- 16,276
Vinen
God is dead
- 2,791
- 497
I'm still in a good position here. Going to wait and see where the stock is in a few months. It's no longer feeling like the handcuffs it once was.
Hope you had some EMC stock-
Noodleface
A Mod Real Quick
- 38,371
- 16,276
Noodleface
A Mod Real Quick
- 38,371
- 16,276
Vinen
God is dead
- 2,791
- 497
People that write XML reading/parsing as just raw strings and substrings grinds my gears. I can understand it if you're doing non-complex operations on the document but dear lord I was asked to just extend this service by a little bit and I'm going to have to basically rewrite the entire thing because they don't DOM the document despite reading and updating nodes. So the service currently can't handle updating the document if multiple nodes of the same name exist, it can't perform complex matching, it can't reliably add new nodes to the document. Luckily since I'm in here gutting it anyways I'm getting a ton of "Oh good you're finally doing that? It needs to do this as well." requirements from people since no one wanted to take the time to actually fix the damn thing.
And despite my love/hate relationship with Groovy ... god damn does it make working on XML easy
And despite my love/hate relationship with Groovy ... god damn does it make working on XML easy
Cad
scientia potentia est
- 25,847
- 50,774
Its shockingly common in the Hadoop ecosystem. Since you process hundreds of millions of documents if you can avoid DOM'ing the object it really does speed up your job executions. But the problem is people tend to not understand where that demarcation lies with "Should I string parse or should I use an actual XML parser?"
Cad
scientia potentia est
- 25,847
- 50,774
If you're processing that many docs, my thought would be whatever accumulated errors you're going to get by trying to manually parse XML overshadows the savings. Because if you're not just looking for something quick in the file, you'll probably create a quick library to help you parse certain things, then you extend it a little here and there to do things you come up with... pretty soon you've written and are maintaining your own half assed XML parser. Seems better to avoid the errors by using a commercial XML parser and just configure it the way you want for the speed/depth you need rather than trying to half ass it.
I get it that it'd be application dependent but I'd have trouble coming up with a use case where just string parsing makes sense?
My rule of thumb is for reading I just string parse if I'm updating then I switch to a full XML parser. If I can get away with just getting what I need from like StringUtils.substringBetween(str, "<jobStatus>","</jobStatus>") I'm not going to pay the overhead to load that up into a SAX parser. But the issue I'm running into is the XML is more free-form and I don't always know what I need to get and/or update underneath the document (I know I need to go three levels deep but the tag names are user input) so I simply have to use some form of xpath engine.
moontayle
Golden Squire
- 4,302
- 165
We use XML for data needed to run our front end. I was running a proof of concept to gather data and update the display accordingly and ended up setting up something like 20+ POJO classes, a couple of them something like 5-6 tags deep. It's kind of silly but it has to be done this way to get the data we need.
Noodleface
A Mod Real Quick
- 38,371
- 16,276
ShakyJake
<Donor>
- 7,967
- 20,085
Unless it's not a well-formed XML doc, I usually write serializable classes that serialize into XML. Way easier to work with object properties than screwing around with elements and attributes.