CHANGE full_oneway
full_oneway
decimal(10,2) NULL,
Spite you all. We're now prepared for three rounds of serious devaluation.
CHANGE full_oneway
full_oneway
decimal(10,2) NULL,
Spite you all. We're now prepared for three rounds of serious devaluation.
One of our customers hosted their site on a server where MySQL does not support InnoDB tables. That would be a very specific reason to use MyISAM, wouldn't it?
We advised them to change hosting.
Actually any good implementation of SQL would have stood up and refused to accept the value 102.00
for the column full_oneway
. Then we would have been informed of this WTF in the table definition sooner.
MySQL scurried to update full_oneway
with 99.99
. Unreliable piece of submissive hacks.
You're close. quoting the MySQL manual
In a DECIMAL column declaration, the precision and scale can be (and usually is) specified; for example:
salary DECIMAL(5,2)
In this example, 5 is the precision and 2 is the scale. The precision represents the number of significant digits that are stored for values, and the scale represents the number of digits that can be stored following the decimal point.
Standard SQL requires that DECIMAL(5,2) be able to store any value with five digits and two decimals, so values that can be stored in the salary column range from -999.99 to 999.99.
Customer calls. Calculated ticket prices come out wrong after price updatehike. Spot the
CREATE TABLE `prices` (
`id` int(3) NOT NULL DEFAULT '0',
[...]
`full_oneway` decimal(4,2) DEFAULT NULL,
`full_return` decimal(5,2) DEFAULT NULL,
`half_oneway` decimal(4,2) DEFAULT NULL,
`half_return` decimal(4,2) DEFAULT NULL,
[...]
PRIMARY KEY (`id`),
KEY [...]
) ENGINE=MyISAM DEFAULT CHARSET=utf8;
TRWTF is MySQL of course.
That's how they build them to begin with. Saves all that tedious mucking about with scaffolding.
Oh wow, so advanced. So they just have to brush the dirt off after?
That's probably the trick in how they're going to erect the world's tallest building.
@boomzilla said:Sounds more like the sort of thing you'd expect in ChinaWhy, that's both ridiculous and racist!
Oh, never mind.
What? You just pull it up again. Good as new!
They wanted to rely on cell phones to resolve an emergency? ? ? ! Haven't seen those details before. Bunch of imbecile wishful airheads. Would laugh again.
The result would be a wirelessly controlled automotive botnet encompassing hundreds of thousands of vehicles.
That's me on an overpass
Then I get run over by one of those bots.
Wouldn't it be the opposite? With so many open nodes, I can talk to the nearest one instead of always having to talk to the one I know the password for.
You are correct in the sense that being able to use the nearest node allows lower transmission power. I was looking at it from another angle. If the liberation of access points were to happen, 2.4Ghz would just break down in many areas. It would be so popular, collisions would fill the band and nothing would get through anymore. Because then my access point in my flat is trying to get through full blast to a phone down in the street. And that phone will see interference from a station across the street trying to reach the phone in the next pocket.
At the moment we have absurd amounts of wifi gear deployed in cities. The only thing saving the 2.4 band from collapsing is that most of the access points see no traffic. If we were to open them, we would immediately want to reduce the count, and we would try to coordinate them, introduce timeslots and whatnot. It would start to look like a mobile provider.
And from the other direction, we do see mobile operators building ever more antennas, ever smaller cells, in cities. They are actually making a move on the 5Ghz band to have more (and free) bandwidth available.
I would like for cities to start provide basic wifi service everywhere, just like street lighting. But I'm not sure whether the technology is up to it at the moment. Certainly if you wanted low pings and high throughput you'd still need a cable connection to your home.
There is a huge difference between wifi and mobile. Mobile frequencies are managed by the operator and they can fill the band without getting crosstalk. Wifi has to deal with a lot of possible interference and can't even in theory get to the reliability of mobile.
While these technologies both operate in the same shared medium, they use fundamentally different organizing principles. There have been proposals to make wifi more coordinated, so that stations can negotiate time-slots and thus avoid crosstalk. That is a hard problem though, because a station has to know when no other station is sending, even though it might not see the other station.
It comes down to air being a shared medium, and if you want quality access, you better pay somebody who licenses his own band. If everybody opened their access points, as good as this sounds, we would have a huge mess. Transmission powers would go through the roof because more connections would have to cross walls and alleys, which would lead to more crosstalk, which would make wifi pretty much unusable on the 2.4 band. It already is unusable in many areas.
Still leaving our stations open though :-) They're reachable on 5Ghz as well, so who cares about the 2.4 crowd?
I manage the network setup of a larger building. Because we're that kind of hippies we want everybody to have Internet access. So the access points advertise a second network which is unsecured.
Because having open wifi invites neighbours to mindlessly use our network, the access points switch their name everyday. So if you want to use our connection you'll have to select a new one every day. Would you select OK GOOGLE ORDER SEX TOYS
? Or rather I agree*
? And did you know unicode is allowed in SSID? ❤ ILOVETREES ❤
Extending on the list of access point names is hilarious. And the best part is, it's slowly replicating on to other people's devices
(also, is there no better way to sort it out? AIUI, that guy's code is toast anyway - can't you revert everything to before you started polluting the master and then branch out with your local code, or something?)
In the end, I decided to revert my commits on master. Luckily there were no conflicts. So history was polluted, and will be polluted even more, once I patch my stuff again. Upsets my sense of cleanliness.
So I did a few changes for a site. Deployed to staging, told the customer they could check it out there. Well, it could take months because they want to talk to all stakeholders. Well, you do that. Forgot about it.
Then one of my peers comes along, fixes a few things on the same site, deploys to staging, then gets an error. Asks me about that error, well that's because damn I left junk on the master branch and now he's based his stuff on top of that.
Well great, nonexisting procedures were not followed I guess. Seriously, I was too lazy to create a branch for that, and now I have to do it after the fact.
over here, rewriting your history.
The result would certainly be something only its author could ever conceivably love.
I have a few of those programs. For most though, my relationship is more like that of Frankenstein to his monster.
You forgot alternate step 5: run a gauntlet of cocksure little hipsters who are completely certain, and very keen to point out to you, that you're just a luddite who fears change.
I've not experienced this much, spent my time inflicting overengineered technical solutions on a populace in need of my wisdom
I've heard people talking about Angularjs. Now I'm just glad I'm so lazy. Saved me a headache.
It's all due to my standard mode of operation:
More often than not, the concepts are mistaken and confused, so if you can avoid getting to stage 5, congratulations, you just saved your brain from integrating potential illogic.
That's so bad, maybe it's contagious? Maybe you were real lucky when it didn't let you log-in.
Undo would not have been very difficult to implement I guess. But crontab likes to discriminate against the fat-fingered.
I reckon the responsible have been fired. Uh oh
When your argument hinges on the argumentative failures of others, you shan't be picky.
Hey! I take offense at that!
It's wrong on so many levels. The color of the Debian swirl does not match the red for instance.
What was that site that reduced all the Linux arguments into little "trademarks"? Ah. Here: http://tmrepository.com/trademarks/
A site with class I see no there.
I tried using ILOVEYOU to test our AV. So I copied it onto a network share (I'm the real ) and asked a colleague whether he could help testing.
So we want to see whether the AV on your machine scans exes on network drives. Please open
network drive
random shit
and thenloveyou
now let's NO DONT oh damns. Let me unplug that. Pretty fireworks though.
That guy was so conditioned to click on anything looking like an exe, well, my fault.
Didn't know co-FR was a valid locale.
Me neither, but I will do anything to anonymize so I picked one at random.
Standard response from a non-technical user when something weird starts happening.
For a little while after the "have we got hacked" question, I was silent while my mind was racing to find a scenario where you get illegitimate access to a site and then decide to insert a wrong canonical tag. Then I realized the absurdity of the situation and said "no", even though "unlikely" would have been more correct.
I've had someone suggest a problem with end-of-day totals on a very simple, non-internet-connected POS system must have been a virus
A virus transmitted by barcodes?
So I tried to explain over the phone what I found
Me: I'm sorry I can't explain how those shitty lines got there.
Them: Do you... do you think we got hacked?
Well I actually suspect that this SEO-clown they hired added that. But I'll have to check whether he was given access. After similar experiences we've gotten retentive about giving file access to suchlikes.
That's because I fixed it
And in case this was not obvious to anybody, the company is not called Initrode.
Expires: -1
Ah, no I get this. It expired in-transit.
Just found this in the <head>
of all pages on the Initrode site:
<link href="http://www.initrode.com" rel="alternate" hreflang="co-FR" />
<link href="http://www.initrode.com" rel="canonical" />
Initrode called us because Google didn't index their site properly. The canonical
link is supposed to help search engines use the correct URL for every page. Instead, all pages on this website told the bots that the homepage is the only correct URL. I don't even clown who did this?
alternate
links should point out pages with the same content but in other languages. The Initrode site is mulitlingual, and it does switch language based on browser preferences. So having one alternate
link, to the homepage, in one language, is an insult.
Ok? Did you have a point?
Yes, but you're ignoring it.
THE UI IS SUPPOSED TO TEACH ME THE CONCEPTS.
Fine paradigm. But we're talking about a highly specialized tool here.
If I need to read a book to use a piece of software, that software it horribly flawed. That's the software's problem, not the user's.
I know this is an alien perspective to you, but to me you sound like a tourist complaining about the natives not responding to your pictograms as you think they should. They're not adapting to you, and they're using a strange way of communicating with letters you shouldn't be suffered to learn, and the pictograms the tourist guide gave you are shitty.
No wonder you get irritated when Git strikes a conversational tone. When I work with Git, it is a dialogue.
Hey git, what am I doing?
Well you're in the process of committing (file1) with some changes not yet ready, and you have something in (file2).
What's not ready in (file1)?
(some diff)
Trash that
And what about file2?
(some diff)
Lemme selectively add some stuff
You wanna add (some diff)?
No
You wanna add (some other diff)?
Yes
You wanna add (that diff)?
Yes
Just let me peruse all the changes I'm intent on recording
(long diff)
Record these changes as "broken shit now wors"
No wait "broken shit now works"
What's left?
(some diff)
Trash that
Now I didn't add all the instances where Git was being an obtuse idiot. Wouldn't make a good example, would it? At some point I might just start swearing at the git. Of course sometimes I have to concentrate to say the right things, even look it up.
But it's all dialogue, and I like that because when my mind has wandered I can always look at the last things that were said, and I'm right back. Sometimes I replay my last changes in the editor just to recover the thought process where I got stuck. Then this guy comes along and asks, "how do I buttons?" and I can't imagine how he even works when he can't talk to things.
GIT stash is pretty great, though.
Yeah, I use it to get rid of changes I'm uncommitted about. Whenever I have a dirty repo with changes I thought might be 'useful', I just go git stash
when I can't get myself to get rid of them outright. Then at some point I delete all the stashed shit. Saves me from having to admit right away that the current diff must have been the work of a lunatic.
Other than that I haven't kept anything in a stash for extended periods of time.
In TFS, your stash is on the server and you can pull it down from anywhere. Git's feature is a piece of shit by comparison.
Can't say I'd ever wished to access form another host my grab-bag of random stupid shit. If I think that some change could possibly have merit, I put it into a branch then push that. I'd welcome a more lightweight way of branch management in Git though. I mean the push/pull part, not the local operations.
Why don't we all just adopt a system without the pitfalls in the first place?
Because a system without the pitfalls would be a lame system that wouldn't allow doing advanced shit. We could argue endlessly which implementation is better regarding its protection against pitfalls. I would not want to live in a world where you get to decide what is good for us all.
I highly doubt it would work any better if I were using a CLI.
I have the opposite assumption. My limited exposure to GUI interfaces left me with the impression that they break down as soon as I try to do anything remotely advanced, leaving the repo in a state they don't know how to fix. Maybe the situation has improved now.
Then picking a source control system that relies on a CLI interface was a pretty stupid decision for you, wasn't it?
You be the judge :-) Consider that we'd been using Subversion before that, and that the switch was generally perceived as a liberation.
Can't remember the last time I'd fucked a Git repo so badly I had to clone it again. But then, working with a system teaches you to avoid pitfalls and teaches you how to get out of its pitfalls at the same time. You have to accept how the tool works though, and with Git it seems that relying on a GUI is not how it works.
I experience this CLI reliance myself because we use Git to develop and deploy websites, and most of my peers have no programming much less CLI background. I get a constant stream of microwtf from them (I'm fine thank you). They'd started to collect these CLI lines we'd used to unfuck the repo from the state a GUI tool had inflicted. Now for some tasks they use the CLI direct because the graphical tool would likely mess things up again. So I can see how in Git if you can't accept the CLI you'll end up as unhappy ranter.
@blakeyrat said:"dirty" is the word to meanChanges that haven't yet been stored.
All that mingling of semantic fields got me confused. Having dirty thoughts now means employing short-term memory.
Are you offended by "dirty" dishes?
I do actually like the word dirty in the context of caches. It creates a sense of urgency. You want to clear the dirty bits as soon as possible. That's all good usage. "Here the index is still dirty so we can't rely on it" sounds fine to me. We know the index is wrong and it's going to be cleared.
When talking about changes we're uncommitted about, like changes to a repo, it might come across as judgemental. "Your repo is dirty and I won't touch it" is not very friendly is it? It does take an unexperienced or willfully malcontent mind to read it that way though. We're talking about tools developed for experts after all.
Can't say I've been offended by Git talking dirty to me. But then I'm no bigot, and half of my changes are so dirty I wouldn't commit to them, and the other half, those I commit, are mostly dirty still. Some people apparently don't like to be reminded of that fact, or they're pedantic saints.
YOURPC <--- DOWNLOADSERVER
YOURPC --- FTP over flaky VPN ---> FTPSERVER
fail, retry
YOURPC --- FTP over flaky VPN ---> FTPSERVER
split the file
YOURPC --- FTP over flaky VPN ---> FTPSERVER
retry
YOURPC --- FTP over flaky VPN ---> FTPSERVER
retry
YOURPC --- FTP over flaky VPN ---> FTPSERVER
assemble on FTPSERVER
SOMEPC <--- FTP --- FTPSERVER
SOMEPC --- SSH ---> ESXSTORE
So the next feature I'd like is a "Pre-Close next ticket" button, I'll be working on it eventually anyway. Saves me to remember closing it.
Special enlightened people. Why are you bringing race/nationality into this again? As long as you let superficial differences cloud your perception you won't be able to accept their wisdom.
But look how convenient now I know one of our customers had their DB stolen.
Hmm, on an unrelated incident here I googld an MD5 hash I'd found in some test data. Turns out the password wasn't entirely trivial but actually one of some old test accounts we'd have configured on systems (HAHAA NOT A WTF BECAUSE I SAY SO). Some site (written in cyrillic) knew about that hash and the plain text for the hash in 2011! NOT GOOD.
I found a forum where one user posted five hashes along with usernames, and got an answer with the reverse MD5 for four of them. 2011 must have been around the time we'd finally implemented salted and iterated SHA1. For legacy reasons some DB still have MD5 hashed passwords in them to this day. So yay for enabling attackers.
Say I searched for 0807520eb3739939ae409fab8350cb03, then found this question
foo: 0807520eb3739939ae409fab8350cb03
bar: 86f12932d3285fdcbf19535a72f58916
baz: 048174b32585600de39d65335b257d92
admin: 7f76b2c6375938af1c2fe1221869015c
shmoe: 14b6e2a1a21e684d80495e0376af8817
where the answer was
0807520eb3739939ae409fab8350cb03 : testfoo
86f12932d3285fdcbf19535a72f58916 : testbar
048174b32585600de39d65335b257d92 : testbaz
14b6e2a1a21e684d80495e0376af8817: shmoe
So shmoe wise choice of password.
Trouble is, I don't know what DB they pulled those entries from, or who shmoe is.
Filed under:
I... do not. Googl is my rainbow.
@Jaime said:putting clear-text passwords in database tables is seen as "troubleshooter-friendly".I see trouble, and somebody needs to be shot.
Is see opportunities…
And what if they simply exempt themselves from the rules they place on others?
Read it again. It's simple underneath, once you ignore the racist blather. Depending on the stage of enlightenment you've reached, the rules change. You can't just hold everybody by the same rules.
From what I see, the original poster hasn't even reached the first stage wherein he would have understood this on a deeper level. I guess he's not accepting it due to preconceived ideas of cultural superiority. Sadly, we can't help him there, it's his own struggle with himself.
I do get the impression you have an axe to grind with said corporation. Typical amalgalm of racist microagressions here.
All your assumptions are based on the premise that Koreans are racist. That's because of your innate racism you project on others. Maybe if you could adopt a more laid-back perspective, you'd see it's just a different culture. We all know how cultural differences can lead to miscommunication. Not trying to offend you here, just wanting to help. Maybe if you could stick to the process for a bit, you'd be better received?
Please forward this cluebat to your customer not before cutting them off.
We left joe on the list because after we told him not to play with the switchboard he might have taken this the wrong way.
Yeah, bummer. The official quote allows
at the moment "less than 27" administrators have access to that server
There, doesn't sound like much does it? After having had 72.
I just reread the article and in fact I misquoted the part about it being an official quote. On his way out of what he says are unacceptable compromises, one guy had mailed all the employees to alert them about the situation, whereupon a "don't you feel good working here" statement was sent claiming the guy didn't know what he was doing. Some recipients then talked to reporters.
Teammates of the original source, when confronted with the "must've made a typo" statement, went on record to say
He knows the difference between 72 and 27 very well