|
Trust me Eppa, you can change the oil in your car.
It is literally unscrewing one cap, draining the fluid, then replacing the cap on the bottom, and replacing the Oill through the cap on the top.
I'm just salty that the old farts that make decisions have no idea what the fuck is happening. I suppose that is just life though.
|
On September 29 2016 12:46 iCanada wrote: Trust me Eppa, you can change the oil in your car.
It is literally unscrewing one cap, draining the fluid, then replacing the cap on the bottom, and replacing the Oill through the cap on the top.
I'm just salty that the old farts that make decisions have no idea what the fuck is happening. I suppose that is just life though.
As one of the guys who manages and supports our reporting environment - alternate perspective. We have a front end reporting interface (BusinessObjects) that we use to deliver data from our database in what are called "Universes". these are basically masks and windows on the underlying database to make consumption easier for end users.
Now, I have no idea what your database is like. But we don't often like end users to query straight from the database. The user who "knows enough to be dangerous" is a common thing - the user might understand SQL and basic database structure, but every companies' databases are different. Some are structured well, some are structured poorly, some don't have security where they should, etc. If an end user isn't familiar with a particular database, it can be very easy to get lost or build bad joins that cause undue strain on the system.
I don't know the exact situation, so I could be missing the mark. But if you're not someone who normally does database queries, there are valid reasons to keep you out.
|
On September 29 2016 13:14 jcarlsoniv wrote:Show nested quote +On September 29 2016 12:46 iCanada wrote: Trust me Eppa, you can change the oil in your car.
It is literally unscrewing one cap, draining the fluid, then replacing the cap on the bottom, and replacing the Oill through the cap on the top.
I'm just salty that the old farts that make decisions have no idea what the fuck is happening. I suppose that is just life though. As one of the guys who manages and supports our reporting environment - alternate perspective. We have a front end reporting interface (BusinessObjects) that we use to deliver data from our database in what are called "Universes". these are basically masks and windows on the underlying database to make consumption easier for end users. Now, I have no idea what your database is like. But we don't often like end users to query straight from the database. The user who "knows enough to be dangerous" is a common thing - the user might understand SQL and basic database structure, but every companies' databases are different. Some are structured well, some are structured poorly, some don't have security where they should, etc. If an end user isn't familiar with a particular database, it can be very easy to get lost or build bad joins that cause undue strain on the system. I don't know the exact situation, so I could be missing the mark. But if you're not someone who normally does database queries, there are valid reasons to keep you out.
Yeah, I agree that there are some valid concerns, I don't think they should let me fart around with the source database or anything like that... quite frankly I am not an expert and likely wouldn't want to fuck around with the actual back end. I was more thinking a simple copy of the schema / data on a flash drive in a .mdf or something.
I dunno, I guess that's too much work and they can't find an extra machine to run the export on or something. Not sure what kind of export runtime there would be on something like that. I think sometimes I take computing power for granted because my machine at work is about as capable as it gets without it being a server in its own right, so could just be we don't have a machine.
I also know that the two managers making the decisions are both under the impression that all coding is some arcane bullshit where magical things come from the ether.
It is just frustrating that all the data I could ever possible want or imagine is just right there, just out of reach. Instead I am basically making guesses using rules of thumbs from books. Which is dumb, because if they weren't going to use the data for anything, why even bother spending the hundreds of thousands of dollars buying all the equipment, writing the software, maintaining the database, etc at all?
|
dunno what your specific situation is, but my company is required to keep a whole shit load of client data on file for 3 years after the end of a contract unless we're explicitly asked to delete it. we could theoretically use it (it's basically de identified health data) to feed into various models b/c we're contractually allowed to do so, but it's a hilarious pain in the ass. plus apparently our oracle compression license expired, so we cant actually access this brick of data. :>
|
I dunno, I don't even think for the usual scale of SQL the database is even that especially large. It is just recorded sensor data on some equipment for basically every project we've installed in the last 9 years. Sounds like a lot, but it is really only maybe 100 site installations a year with maybe 5 different tables. Like I'd guess the database is several orders of magnitude smaller than LL.
But it is enough data that it would give me exactly loading scenarios of all my equipment and I could build and design new stuff that could last until it rusts out or alternatively design it to a very specific design life like +/- 1%. Obviously either way is fantastic and would save the company big bucks.
Without access though I'm guessing at loading, loading over time, number of loading cycles per job etc... and suddenly I can predict with doing 3x as much educated guesswork and beven able to design to a specific design life +/- ~30%. Or over design the crappy out of it. Whether we are using the equipment internally or selling it, it really kills my ability to make good models.
There could be a legit reason that it is unfeasible, just i honestly have no idea because the message is likely from manager 1 to manager 2 to manager 3 to me... and none of those managers has a clue what any of it means. And that obviously just makes it more frustrating.
Yay corporate efficiency!
|
The database and coding is probably so badly made they dont want to traumatize you. Oh the shit I've seen......
|
On September 29 2016 17:24 Jek wrote: The database and coding is probably so badly made they dont want to traumatize you. Oh the shit I've seen......
This is likely the truth of it. When I first moved into the DBA side of my job, dealing with the monstrocity that is the governments setup was.... Nightmare fuel.
Old people made the language, but they sure as hell can't do anything constructive with it.
|
Guys, Fractured Space is really fun, give it a try
|
On September 29 2016 14:15 iCanada wrote: I dunno, I don't even think for the usual scale of SQL the database is even that especially large. It is just recorded sensor data on some equipment for basically every project we've installed in the last 9 years. Sounds like a lot, but it is really only maybe 100 site installations a year with maybe 5 different tables. Like I'd guess the database is several orders of magnitude smaller than LL.
But it is enough data that it would give me exactly loading scenarios of all my equipment and I could build and design new stuff that could last until it rusts out or alternatively design it to a very specific design life like +/- 1%. Obviously either way is fantastic and would save the company big bucks.
Without access though I'm guessing at loading, loading over time, number of loading cycles per job etc... and suddenly I can predict with doing 3x as much educated guesswork and beven able to design to a specific design life +/- ~30%. Or over design the crappy out of it. Whether we are using the equipment internally or selling it, it really kills my ability to make good models.
There could be a legit reason that it is unfeasible, just i honestly have no idea because the message is likely from manager 1 to manager 2 to manager 3 to me... and none of those managers has a clue what any of it means. And that obviously just makes it more frustrating.
Yay corporate efficiency!
Your request seems reasonable, so I'm not sure what the deal is.
|
Opened Golden Nat Pagle... Which means I opened any other actually useful Legendary I need
|
On September 29 2016 23:07 Requizen wrote:Opened Golden Nat Pagle... Which means I opened any other actually useful Legendary I need  But it's golden!
|
I'm going to New york over the election pretty much. 5-9th. It's a bit scary what with all the terrrorr stuffs....
|
On September 30 2016 00:01 Duvon wrote: I'm going to New york over the election pretty much. 5-9th. It's a bit scary what with all the terrrorr stuffs.... Say hi to the NY TLers while ur there
|
On September 30 2016 00:01 Duvon wrote: I'm going to New york over the election pretty much. 5-9th. It's a bit scary what with all the terrrorr stuffs.... I'd be less worried about the terror and more worried about the riots when someone wins. Doesn't matter who at this point.
|
On September 30 2016 00:13 Requizen wrote:Show nested quote +On September 30 2016 00:01 Duvon wrote: I'm going to New york over the election pretty much. 5-9th. It's a bit scary what with all the terrrorr stuffs.... I'd be less worried about the terror and more worried about the riots when someone wins. Doesn't matter who at this point. We'll be staying on Manhattan so I guess we'll be kinda safe? dunno.
|
On September 29 2016 22:06 jcarlsoniv wrote:Show nested quote +On September 29 2016 14:15 iCanada wrote: I dunno, I don't even think for the usual scale of SQL the database is even that especially large. It is just recorded sensor data on some equipment for basically every project we've installed in the last 9 years. Sounds like a lot, but it is really only maybe 100 site installations a year with maybe 5 different tables. Like I'd guess the database is several orders of magnitude smaller than LL.
But it is enough data that it would give me exactly loading scenarios of all my equipment and I could build and design new stuff that could last until it rusts out or alternatively design it to a very specific design life like +/- 1%. Obviously either way is fantastic and would save the company big bucks.
Without access though I'm guessing at loading, loading over time, number of loading cycles per job etc... and suddenly I can predict with doing 3x as much educated guesswork and beven able to design to a specific design life +/- ~30%. Or over design the crappy out of it. Whether we are using the equipment internally or selling it, it really kills my ability to make good models.
There could be a legit reason that it is unfeasible, just i honestly have no idea because the message is likely from manager 1 to manager 2 to manager 3 to me... and none of those managers has a clue what any of it means. And that obviously just makes it more frustrating.
Yay corporate efficiency!
Your request seems reasonable, so I'm not sure what the deal is.
I think either the people making the decisions are complete idiots or the hardware limitations when they started compiling this data made them have to combine fields in some sort of binary hash to limit the scale of the database and it's required number of processes at the shit field laptop... you could have 4 fields in one binary string; which would certainly be reasonable if they had fancy plans at the time given how shit laptops were at the time. At the same time if this was the case you'd thing they'd make a quick code to unhash it.
In which case I'd need a copy of the softwares source code to reverse engineer the hash. I'd be comfortable figuring it out, but I could also see them being apprehensive about giving random mechie a copy of the source code. Shrug. Who knows, might be useless to me anyway in that case depending what kind of ORM layers they had / still have going. But I have no idea. Perhaps it could be both.
|
On September 30 2016 00:21 iCanada wrote:Show nested quote +On September 29 2016 22:06 jcarlsoniv wrote:On September 29 2016 14:15 iCanada wrote: I dunno, I don't even think for the usual scale of SQL the database is even that especially large. It is just recorded sensor data on some equipment for basically every project we've installed in the last 9 years. Sounds like a lot, but it is really only maybe 100 site installations a year with maybe 5 different tables. Like I'd guess the database is several orders of magnitude smaller than LL.
But it is enough data that it would give me exactly loading scenarios of all my equipment and I could build and design new stuff that could last until it rusts out or alternatively design it to a very specific design life like +/- 1%. Obviously either way is fantastic and would save the company big bucks.
Without access though I'm guessing at loading, loading over time, number of loading cycles per job etc... and suddenly I can predict with doing 3x as much educated guesswork and beven able to design to a specific design life +/- ~30%. Or over design the crappy out of it. Whether we are using the equipment internally or selling it, it really kills my ability to make good models.
There could be a legit reason that it is unfeasible, just i honestly have no idea because the message is likely from manager 1 to manager 2 to manager 3 to me... and none of those managers has a clue what any of it means. And that obviously just makes it more frustrating.
Yay corporate efficiency!
Your request seems reasonable, so I'm not sure what the deal is. I think either the people making the decisions are complete idiots or the hardware limitations when they started compiling this data made them have to combine fields in some sort of binary hash to limit the scale of the database and it's required number of processes at the shit field laptop... you could have 4 fields in one binary string; which would certainly be reasonable if they had fancy plans at the time given how shit laptops were at the time. At the same time if this was the case you'd thing they'd make a quick code to unhash it. In which case I'd need a copy of the softwares source code to reverse engineer the hash. I'd be comfortable figuring it out, but I could also see them being apprehensive about giving random mechief a copy of the source code. Shrug. Who knows, might be useless to me anyway in that case depending what kind of ORM layers they had / still have going. But I have no idea. Perhaps it could be both.
Something like that is possible, yeah. I know we're currently struggling with some legacy data structures that were put in place a decade and a half ago and really weren't meant to scale as things grew.
|
Czech Republic11293 Posts
Damn, looking at Civ6 it ACTUALLY looks really good. I haven't been this excited for a game in a really long time.
|
I have moderately sized regrets about not getting Quarterfinals tickets when they went up. All the resellers are stupidly overpriced, though.
|
On September 30 2016 02:20 Scip wrote: Damn, looking at Civ6 it ACTUALLY looks really good. I haven't been this excited for a game in a really long time.
Yeah, the RPS review was practically glowing and with 47 hours put in there's some confidence we're not walking into another CIV:BE situation.
|
|
|
|
|
|