|
DarkHorse posted:Anyone else feel like this is your job Nope, it's more like this. 8 hours a day, everyday, even on days off: https://www.youtube.com/watch?v=QCniMXdbO6c
|
# ? May 31, 2014 17:49 |
|
|
# ? Jun 5, 2024 19:34 |
|
It's so badly looped
|
# ? May 31, 2014 17:53 |
|
DarkHorse posted:Anyone else feel like this is your job Yes. So very very much.
|
# ? May 31, 2014 18:02 |
|
Paladine_PSoT posted:Yup, 5 ridiculous months of job searching ended with an offer letter yesterday. New position is contract but at a 45% raise over my last position, same benefits. I'm very confused about your job post if this contact is where I think it is
|
# ? May 31, 2014 18:06 |
|
Caged posted:It's so badly looped There's a better one but I couldn't find it.
|
# ? May 31, 2014 18:58 |
|
We deployed an untested patch because it was a "small fix" and nearly broke some equipment worth $125 million. gently caress my life. Lesson re-learned
|
# ? May 31, 2014 22:52 |
|
Wibla posted:We deployed an untested patch because it was a "small fix" and nearly broke some equipment worth $125 million. gently caress my life. Lesson re-learned This is ammunition for you to use any time one of your bosses who doesn't understand good IT practices gets uppity about how long you might be taking to implement a thing. "Remember last May when, in the interests of expediency, we deployed something without testing and nearly lost 125 million dollars worth of equipment and who knows how many man-hours it would have taken to replace and reconfigure it? What we're doing now will prevent that. If you'd like to sign something saying you'll take full responsibility for that kind of loss, having been informed of the risks, we can hurry it up for you."
|
# ? May 31, 2014 23:31 |
|
Che Delilas posted:"Remember last May when, in the interests of expediency, we deployed something without testing and nearly lost 125 million dollars worth of equipment and who knows how many man-hours it would have taken to replace and reconfigure it? What we're doing now will prevent that. If you'd like to sign something saying you'll take full responsibility for that kind of loss, having been informed of the risks, we can hurry it up for you." Sounds like entrapment to me.
|
# ? Jun 1, 2014 00:50 |
|
GreenNight posted:Sounds like entrapment to me. I love how Entrapment now seems to mean "Telling me that this could go wrong doesn't make it my fault, even if I'm the one who OK'd it. I still get to blame you, even though I forced you to do it."
|
# ? Jun 1, 2014 02:15 |
|
Entrapment means you made me look bad by doing the correct thing AND YOU DID IT ON PURPOSE DIDN'T YOU
|
# ? Jun 1, 2014 06:04 |
|
evol262 posted:I'm very confused about your job post if this contact is where I think it is Fair enough, I had two jobs that I was looking at. The first is the one I took, the second was for a startup company in Redmond that a friend works for. I opted to not take that one because of a few reasons, but the job itself could be a good opportunity for someone and I'm trying to help the friend find a potentially qualified candidate because they're a friend.
|
# ? Jun 1, 2014 09:33 |
|
Paladine_PSoT posted:Fair enough, I had two jobs that I was looking at. The first is the one I took, the second was for a startup company in Redmond that a friend works for. I opted to not take that one because of a few reasons, but the job itself could be a good opportunity for someone and I'm trying to help the friend find a potentially qualified candidate because they're a friend. That job posting actually got me kind of excited. I'm totally unqualified for it but I was just thinking, that'd be a neat job, I should continue to acquire skills that will push me in that direction.
|
# ? Jun 1, 2014 09:49 |
|
What's the likelihood of getting a software company to pay me for a solution I found for their crappy software? Ticket: Laptop docked, software sits on right screen. When undocked, software still sits on non-existent right screen and you have to go through task manager to maximize the window and get it back. Software support's solution: use the task manager workaround, this is a known issue and we don't plan on fixing it because 5 minutes later I, a first year desktop support, find out how to fix their software via registry edits. Should I be a nice guy and follow up with their support team telling them what to do to fix it? Or should I contact them and hold the solution ransom for 1 hour of billable time? Judge Schnoopy fucked around with this message at 21:33 on Jun 1, 2014 |
# ? Jun 1, 2014 21:31 |
|
Judge Schnoopy posted:What's the likelihood of getting a software company to pay me for a solution I found for their crappy software? They won't pay for it. Because that would make sense.
|
# ? Jun 1, 2014 22:09 |
|
Judge Schnoopy posted:What's the likelihood of getting a software company to pay me for a solution I found for their crappy software? It's not worth their developer's time. They will pay you nothing. Actual answer: start blogging about stuff you do. Put solutions to problems there. Including this.
|
# ? Jun 1, 2014 22:09 |
|
evol262 posted:It's not worth their developer's time. They will pay you nothing. This. This will get you job offers, if you can find useful/interesting stuff.
|
# ? Jun 1, 2014 22:14 |
|
Mind sharing the program? I have that happen with several programs when I go from docked to undocked.
|
# ? Jun 1, 2014 22:58 |
|
Tigerpaw specifically. They designed registry keys to hold a pixel based value of where it was closed. Then there's a key of RestoreSizeOnOpen set to 1. Set to 0 and it opens in the upper left corner every time. It was idiotically simple for them to have told me they couldn't be assed to find a solution.
|
# ? Jun 1, 2014 23:47 |
|
blackswordca posted:
Cheers man, I'll have an extra Ohio gas station diluted whisky and coke for you.
|
# ? Jun 2, 2014 04:12 |
|
Judge Schnoopy posted:Tigerpaw specifically. They designed registry keys to hold a pixel based value of where it was closed. Then there's a key of RestoreSizeOnOpen set to 1. Set to 0 and it opens in the upper left corner every time. You will never hear a company admit "We just don't care enough for this bug." Never, ever, ever. evol262 posted:It's not worth their developer's time. They will pay you nothing. Do this. Either they have better things to do, or their developers are totally incompetent, or any combination of other reasons. Regardless, they won't pay you for this.
|
# ? Jun 2, 2014 06:29 |
|
A hilarious bug came in! I tried to add a work item on a ticket, and was met with this error:quote:PHP Error: Uncaught ADODB_Exception in /kbox/kboxwww/include/KTicket.class.php on line 2632: mysql error: [1064: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 's office.', '12', '0.00000')' at line 1] in EXECUTE("insert into HD_WORK (HD_TICKET_ID, START, STOP, NOTE, USER_ID, ADJUSTMENT_HOURS) values (265, '2014-06-02 09:00:00', '2014-06-02 10:15:00', 'Attempted to repair the Sharp but upon opening the stapler compartment I found that to actually get at the components inside it would potentially take me an hour or more to disassemble the unit. Have powered off the unit. Temporary(?) replacement printer has been installed in <user>'s office.', '12', '0.00000')") Apparently writing '<user name>'s office' breaks the ticket! KACE
|
# ? Jun 2, 2014 14:54 |
|
Sirotan posted:A hilarious bug came in! I tried to add a work item on a ticket, and was met with this error: Seriously. Non parameterised SQL in 2014 jre fucked around with this message at 15:00 on Jun 2, 2014 |
# ? Jun 2, 2014 14:57 |
|
Sirotan posted:A hilarious bug came in! I tried to add a work item on a ticket, and was met with this error: That message means you misspelled the user's name. His real name is "user name>','12','0');drop table HD_WORK;"
|
# ? Jun 2, 2014 15:09 |
|
jre posted:
That's horrifying. Honestly, modern compilers should just refuse to compile non-parameterized queries. "Error: No I will not let you spread your rear end in a top hat THIS wide."
|
# ? Jun 2, 2014 15:16 |
|
BabyFur Denny posted:That message means you misspelled the user's name. His real name is "user name>','12','0');drop table HD_WORK;" I know next to nothing about databases, but I'm guessing this is an attack (injection?) that would wipe a good chuck of that database.
|
# ? Jun 2, 2014 15:17 |
|
Splashy Gravy posted:I know next to nothing about databases, but I'm guessing this is an attack (injection?) that would wipe a good chuck of that database. "Drop table" is SQL for "rm -rf".
|
# ? Jun 2, 2014 15:21 |
|
Splashy Gravy posted:I know next to nothing about databases, but I'm guessing this is an attack (injection?) that would wipe a good chuck of that database. Injection the correct term, yes.
|
# ? Jun 2, 2014 15:23 |
|
Splashy Gravy posted:I know next to nothing about databases, but I'm guessing this is an attack (injection?) that would wipe a good chuck of that database. They aren't using parameterized queries so the user input is passed straight to the SQL server. This allows him to end the insert command and start a new command which is to drop or delete that table.
|
# ? Jun 2, 2014 15:25 |
|
BabyFur Denny posted:That message means you misspelled the user's name. His real name is "user name>','12','0');drop table HD_WORK;" You need to end the injection with a -- for a comment otherwise the messed up SQL won't parse. "user'); drop table HD_WORK; --"
|
# ? Jun 2, 2014 15:26 |
|
peak debt posted:You need to end the injection with a -- for a comment otherwise the messed up SQL won't parse. Sirotan, please do the needful.
|
# ? Jun 2, 2014 16:02 |
|
Moey posted:Sirotan, please do the needful. Bur first, use it to poke around the DB structure and bump up your stats
|
# ? Jun 2, 2014 16:54 |
|
TBH it should be user'); drop table information_schema; -- MySQL also makes it very easy to make it happen off-hours via SLEEP. deimos fucked around with this message at 16:59 on Jun 2, 2014 |
# ? Jun 2, 2014 16:57 |
|
Biggus Dickus posted:Bur first, use it to poke around the DB structure and bump up your stats I'm the only one who even bothers logging work to tickets as it is so I probably wouldn't need to. And it looks like all it takes is using a Sirotan fucked around with this message at 18:09 on Jun 2, 2014 |
# ? Jun 2, 2014 17:03 |
|
Sirotan posted:I'm the only one who even bothers logging work to tickets as it is so I probably wouldn't need to. Quote, not comma, at least I think. And who are we kidding, the reponse will be quotes in the description field are not supported. EDIT: WAIT A MINUTE, why the gently caress is there an EXECUTE( in that statement? EDIT2: Oh god, KACE http://www.exploit-db.com/exploits/27039/ deimos fucked around with this message at 17:24 on Jun 2, 2014 |
# ? Jun 2, 2014 17:16 |
|
deimos posted:Quote, not comma, at least I think. And who are we kidding, the reponse will be quotes in the description field are not supported. Whoops sorry yeah meant quote not comma. And wow, Dell has known about this since last FEBRUARY? I guess it doesn't matter that I can't even submit a bug report then huh. Jesus christ.
|
# ? Jun 2, 2014 18:09 |
|
Che Delilas posted:That's horrifying. Honestly, modern compilers should just refuse to compile non-parameterized queries. "Error: No I will not let you spread your rear end in a top hat THIS wide." PHP isn't compiled, unless you're using hip-hop, and even then its kind of weird. I mean, there are like 8 ways to Sunday to clean user input in php/MySQL stuff. If you're not cleaning user input, you should be placed in a special level of hell.
|
# ? Jun 2, 2014 18:50 |
|
Volmarias posted:You will never hear a company admit "We just don't care enough for this bug." Liar! I've been told just that. Well, it was "we won't be fixing this issue, it's not important" but it's still exactly the same!
|
# ? Jun 2, 2014 19:14 |
|
Zephirus posted:I regularly have to deal with an engineer at a vendor who uses full stops instead of spaces. You need to open the console for that engineer, and set the Shatner_Mode env to 0.
|
# ? Jun 2, 2014 19:23 |
|
DROP TABLE commonly won't work if there are active connections to the database (at least in SQL Server), use TRUNCATE TABLE instead. That'll preserve the schema, and 'just' delete all the rows in it. (I tried once on an old server after we had migrated the db off and it plain wouldn't let me use DROP)
|
# ? Jun 2, 2014 19:24 |
|
|
# ? Jun 5, 2024 19:34 |
|
Caconym posted:DROP TABLE commonly won't work if there are active connections to the database (at least in SQL Server), use TRUNCATE TABLE instead. That'll preserve the schema, and 'just' delete all the rows in it. You can totally drop a table in MySQL mid query, unless the user doesn't have permission. Most users will get it, as most MySQL app's are designed with a (nearly) full permission user in mind.
|
# ? Jun 2, 2014 19:29 |