HNHacker News
TopNewBestAskShowJobs

kevhito

685 karma · joined January 13, 2015

submissionscomments
kevhito··on The Best Way to Not Get Tenure
> no one really cares

Maybe. Or maybe they care and simply have a different perspective on what is the best approach. Or maybe they have different priorities. Optimizing for one variable (e.g. making one specific course awesome) at the expense of all others (hedging against future enrollment trends, pleasing the board of directors & alumni, limited faculty resources, ....) is simply not how universities work.

So I agree with you, somewhat, in some circumstances. In the science side of thing, maybe. But we're also talking about the college's dog policy here. The author seems to think it is completely obvious that he should be free to bring his dog to his campus lab, and shows no awareness that there may be good reasons there is a no dog policy. Maybe there are students with allergies? Or maybe UB has been sued for this in the past? Or maybe its a state law? I don't know.

So reading your comment carefully, it isn't actually obvious if you think it was the author's colleagues who had the big egos and won't listen to criticism, or the author himself.

kevhito··on The Best Way to Not Get Tenure
I think it's mostly just me. It's not so much "get in line", but "before you complain about getting in line, maybe consider why there is a line in the first place".

Getting burned by pissing off one or two people in your department is unfortunate. Pissing of more than half the people in your department? Plus lots of people in other departments? And the administration too? And even the local newspaper?

Either he is the only good guy in a sea of jerks, or maybe he's not quite the good guy he thinks he is. I don't know the which it is, and the article doesn't tell us either.

I'm not sure why this story upset me so much. I think it is because when I started in my department, I saw things I thought were terrible -- courses that hadn't been revised in years, the wrong languages being taught, outdated exercises, poorly-written web pages, cumbersome processes, etc. And I said so, frequently. Thankfully, I had some great mentors to help teach me to slow down and listen to others, and work with others. We've now made lots of changes, updated the curriculum, and done it all together. And some things I thought were terrible I know realize are actually elegant solutions to problems outside of our control (e.g. finite money and time and expertise, and a college administration that needs to think about public perception, alumni, gifting, athletics, other departments, and lots of other things besides "what will make the CS department awesome").

kevhito··on The Best Way to Not Get Tenure
No, you are right, I was perhaps too harsh. But it takes some modesty and humility to pause and consider why the system ended up the way it has, and why the elder's are resistant to change. The author shows no sign of modesty or humility, so it isn't at all clear to me that the elders were snitty or tutting and hissing. In fact, it sounds like there were other issues the author was deliberately ignoring. Finite resource allocation, campus-wide priorities, an MS program, etc.

Being able to convince others, win allies, balance priorities, and just get along with others are important skills, and the author seems to excel at none of these. At least, judging by this post. Elsewhere in this thread, a student suggested that there may really have been some nasty infighting happening, in which case this poor guy may have just been in the wrong place at the wrong time.

kevhito··on The Best Way to Not Get Tenure
I am very thankful to be in a department with almost zero nasty internal politics, and I've heard real horror stories from people I trust about how nasty things can get.

So thanks for providing more context. It's hard to tell from the post whether this person is the cause of or recipient of all this drama. From the way he tells it, it wasn't just the department, but pretty much everyone he interacted with across campus. It wouldn't surprise me if the entire university was poisoned by nasty politics, but it also wouldn't surprise me if a self-assessed superstar would see it that way even if it were not.

kevhito··on The Best Way to Not Get Tenure
Hi, although I'm new here and all of you have been teaching here for 20 years on average, let me tell you why everything you have done with the curriculum is terrible and should be completely rewritten in my style. And of course, I'll have to do all of this myself, since you are all incompetent. And I better teach the first round myself too, because I can't trust you with that either.

So yes, there is a difference between not pissing off people on the committee and "obedience".

kevhito··on The Best Way to Not Get Tenure
> All university departments are filled with miserable gossips.

They are also filled with people who think their own vision and priorities for the intro programming course, operating systems course, networking course, "entire" undergrad curriculum, department and college resource allocation, and campus dog policy, are obviously the only correct and rational choice, and anyone who disagrees is a miserable gossip.

kevhito··on The Best Way to Not Get Tenure
I agree with this. But research isn't everything. And there are at least some hints and signs that this person doesn't know how to get along with colleagues.

> I worked really hard to bring an exciting and rigorous operating systems class to UB.

Why did this effort require working "really hard"? Was it because of obstructionist, jealous, or stupid colleagues? Or people who wanted a boring and unrigourous course instead? Or were there perhaps legitimate reasons why others didn't want to change the existing course?

> I led a complete overhaul of our department’s undergraduate computer science curriculum. It includes two new exciting introductory programming courses that I spent a great deal of time designing.

Let me guess: the existing curriculum was terrible, boring, not at all rigorous, and there was no reason to keep any of it, and the author made sure everyone knew it. And why did the author have to spend a great deal of time? Because no one else in the department was capable of doing as good a job? Because nobody else could comprehend this grand vision?

Everything listed under "speaking out" gives me the same vibe. It doesn't seem to have crossed this person's mind that there are reasons why other people have different approaches to teaching, research, administration, hiring, etc., beyond others being obstructionist, brainwashed, or just stupid. I'm reminded of the parable reminding us [1] to not take down a fence until we have truly understood why the fence was erected in the first place.

And really... bringing a dog to work in violation of a clearly stated campus policy, repeatedly, even after having been warned, then encouraging a student petition and getting your name in a local paper about the incident? That's just asking for trouble.

(Full disclosure: I'm coming up for tenure myself, and one lesson it has taken me 5 years to understand is that people who disagree with me on campus aren't doing so out of spite, stupidity, or carelessness, they often just have different priorities than I do. Just because our department absolutely needs more resources to do a good job handling our rapidly growing student population, doesn't mean the college should make this a priority over other things.)

[1] http://www.chesterton.org/taking-a-fence-down/

kevhito··on [dead]
Title should not be "scraping from my cell" but "scraping from any tracfone account without needing credentials".

I'm not even sure you can call this [1] a vulnerable API... it just plain public, with no authentication whatsoever.

[1] https://www.fastactportal.com/static/balance

kevhito··on Inclusive Design Toolkit
I apologize. I didn't mean to suggest we should design for a "typical human" (even if such a thing existed or could be well defined), and I agree that we should design for a range of user abilities. I was trying (poorly) to discuss their definition "disabled", which seems unhelpful as it seems to be synonymous with "human".
kevhito··on Inclusive Design Toolkit
I think my comment rubbed a lot of people the wrong way, and for that I apologize. Actually, I agree with almost everything the replies argue. My point -- which I did didn't make well -- was that I think using the word "disabled" in the WHO sense is either disingenuous or silly. Silly, because if everyone is disabled at all times, then the word becomes meaningless. Disingenuous in the sense that "not having a range of ability" implicitly really means having an unusually or unexpectedly limited or different (but not strictly larger) range of abilities as compared to some poorly-defined range for a "typical" human, without actually admitting that we are comparing against some standard.

Yes, the standard is vague and poorly defined. And I agree that disability doesn't need to be permanent or easily visible or significant, that it is context dependent, and it obviously isn't binary. I have no qualms with the idea that everyone or nearly everyone is, at some point and in some ways, disabled. And perhaps most importantly, we should disentangle the concept of disability with moral/value judgments.

Still, I think all of the examples I've seen on this thread are implicitly comparing against a standard but explicitly pretending they are not. You mention that you are disabled from reading your screen. Because many humans would have that ability. You didn't say you were disabled because you don't have the x-ray vision needed to see through walls. Just like nobody would say a person is disabled because their body doesn't produce enough fur or whale blubber to survive a new england winter.

kevhito··on Converting atmospheric carbon dioxide into carbon nanotubes for use in batteries
... as compared to the known, ongoing and serious contamination of the environment due to coal plants, of course.

Do you have a citation for the CFL concern? I'm not expert in this area, but my quick checking only reveals this [1]:

> Even if the mercury contained in a CFL was directly > released into the atmosphere, an incandescent would > still contribute 4.65 more milligrams of mercury into > the environment over its lifetime.

Basically the same info from the EPA as well, here [2].

[1]: http://www.popularmechanics.com/home/reviews/a1733/4217864/

[2]: https://www.energystar.gov/ia/partners/promotions/change_lig...

kevhito··on Inclusive Design Toolkit
No. Because you (and WHO) are consistently leaving out the obvious -- all of this is in comparison to "typical" human abilities. According to that definition, everyone living in a northern climate becomes disabled each winter, since none of us can survive outside without special clothing. And if humans could see magnetic lines, we'd all certainly be better matched to our earth environment, so does that mean all humans disabled?
kevhito··on Kenyan girls who code: Mentors spur African tech innovations
As soon as I saw the title, my heart sank a little, knowing that comments like this would soon follow. At least there aren't yet any comments about their looks or why its okay to track them down and harass them because it's just part of Internet Culture. So there is that.

Now, as for your "serious questions". Yes, let's have them. But let's please not pretend that history, culture, and sexism don't exist. And be sure to contextualize your "serious questions", taking into account the specific historical and current challenges facing women and girls in Kenya.

kevhito··on Animal Minds: The new anthropomorphism
Because Turing completeness?

But certainly, there are no doubt emotions, habits, moral concepts, and even "thoughts" that are thoroughly foreign to humans. Not impossible, just foreign.

kevhito··on Show HN: Forgiva – Never saves your passwords but regenerates them
I was responding to this assertion:

> all encryption methods prone to brute-force attacks

The chance of succeeding within our lifetime with a brute-force attack against modern encryption is far less than one in a trillion. So in your words, it is far better than "pretty secure".

kevhito··on Show HN: Forgiva – Never saves your passwords but regenerates them
And if you go that path, "theoretically" an attacker might simply guess your password on the first try when attempting to log in as you, so password "storages" and "brute-force" has nothing to do it.
kevhito··on ORWL – The first open source, physically secure computer
There are reasonable issues that could be raised about various meta-data leaks with full-disk encryption. For example, in a completely naive per-file encryption scheme, the (approximate) file sizes would be visible. But I don't think "brute force" is a concern for reasonably modern encryption schemes. Of course, if they are using weak/short pins with a key derivation function, then that is vulnerable to brute force.
kevhito··on $1M VotePlz Sweepstakes
They need to notify the winner(s) somehow?
kevhito··on UnGoogled Chromium: Chromium with enhanced privacy, control and transparency
Is there something particular about your mom I should take away here? Or moms in general? Or women? Or older people?

My mom, like yours, would have no use for dev tools -- because she's just not interested. And neither would my brother, but my grandma would have loved learning about this stuff if she had lived long enough, and my kids have discovered this "secret hacker mode" all on their own and are delighted.

kevhito··on House panel looking into Reddit post about Clinton's email server
I was getting ready to point out that Hillary really has a large lead, even if the day-to-day talking heads insist on making this and every race/issue seem as if it is 50/50 split. Then I checked 538.com [1]: they have her at 60% chance of winning -- pretty strong lead and hardly a normal time to throw someone under the bus -- but those graphs should be terrifying team Hillary.

[1] http://projects.fivethirtyeight.com/2016-election-forecast/

kevhito··on Ask HN: Strange bug workarounds?
The resistor-vga trick is one I use somewhat regularly. When traveling to give a talk, I sometimes like to practice my talk with powerpoint's "presention mode" in front of me. You can't easily get that mode without a second monitor plugged in. I keep a single bare resistor that can be stuck into two holes in the VGA connector. I keep the resistor inside a folded slip of paper so it doesn't get lost, and the paper has a reminder on it too showing which two pins to connect. Works perfectly.
kevhito··on The math of CSS locks
I agree that "lock" is a really poorly chosen word here. The explanation and diagram with a canal lock on that page is... unusual. It's a cutaway diagram of a physical canal lock, re-purposed as an mathematical graph (with x as the "viewport width" independent axis, and y as the "line height" dependent axis). But then it keeps the center portion moving up and down as if it is still a canal lock, so it can't really be a mathematical function at all.

The word "clamped" should have been used instead of "lock". They just want the text size to scale linearly with page width, but they want to "clamp" the text size so that it always stays within some reasonable (min, max) range. They could have also called it "piecewise linear".

kevhito··on The Imposter's Handbook
And my students have calculators so there is no need for them to know basic arithmetic.
kevhito··on Bounds Check Elimination (BCE) in Golang 1.7
If out of bounds errors were undefined behavior, lifting the bounds check out of the loop would be legal. But in go, it isn't an error. It is equivalent to panic(), which can be caught. If the caller recovers, they should see the partially-completed loop, but lifting it out of the loop would change that behavior.

Here is an example, using your copy function:

https://play.golang.org/p/Cc3Oc3le-9

kevhito··on Bounds Check Elimination (BCE) in Golang 1.7
In C/C++, out-of-bounds memory access is in undefined behavior, so the compiler can assume it is a nop, so it is dead code and eliminate it.

In go, out-of-bounds array/slice access is equivalent to calling panic. So _ = a[i] isn't dead code unless you can be sure that a[i] is in bounds. So yes, I imagine BCE should come before dead code elimination.

kevhito··on What Golang Is and Is Not
It's even worse. The longTimer has fired, and it sent a message on the channel just as it was supposed to. When Reset() is called, it causes a second firing and a second message. Here is the code, corrected to illustrate. The output times are exactly as one would expect.

https://play.golang.org/p/lntgH6tkiF

kevhito··on Upping the volts will make hybrid cars much cheaper
Even the opening sentences are wrong:

> VOLTAGE is to electricity what pressure is to water: the more you have of it the more oomph you get. That is why electrical power lines work at high voltage.

No. Losses in transmission lines are proportional to current squared [1]. High voltage is used because it results in lower current (for the same power), so lower losses.

[1] http://www.bsharp.org/physics/transmission

kevhito··on FreeBSD Core statement on recent freebsd-update and related vulnerabilities
> 3. You don't leave memory corruption vulnerabilities in software to preserve backwards compatibility. It is better to break software briefly than to leave memory corruption vulnerabilities in it.

I know nothing about FreeBSD updates. But my reading was that there is a concern that a misguided patch could break the update process itself, leaving a lot of systems unable to fix themselves. Updating the code that distributes updates is risky.

kevhito··on Interactive Sudoku Zero-Knowledge Proof
This is correct, and key to making this zero knowledge. But "accumulate" isn't quite the right word, I think. During a single round, by itself, Peggy reveals literally nothing about the actual solution -- no information whatsoever -- so one might wonder, how can a bunch of repeated nothings "accumulate" to anything?

Here's how. If Peggy were to use the same permutation repeatedly, revealing different rows/columns/boxes, then Victor can cross-reference the permuted numbers in one revealed row against the same-permuted numbers in other rows. (E.g. Victor might notice that the top left corner has the same as the bottom center tile, which he didn't know before.) And each new reveal allows for more cross-referencing, and soon Victor can learn a lot. Notice that cross-referencing the numbers within a single revealed row don't tell Victor anything -- no number will appear more than once, so all Victor learns is that all the cells are different, which Victor knew already by the rules of Sudoku.

Of course, Peggy uses a different permutation each round, so each round Victor learns nothing, and the different permutations prevent Victor from cross-referencing numbers from different rounds to learn anything that way either.

kevhito··on Fear and Loathing in Linux, or Who Needs /etc/motd (2010)
As a reluctant admin for a half dozen odd home and work systems, and having just dealt with a few clean reinstalls, the /etc/motd issue bit me too. It also reminded me a bit of the horror that grub configuration has become.

When I started years ago there was LILO. It had quirks and was a pain to configure. Then grub came along and it had some great new features -- edit the easy-to-understand config file, and changes would automatically take effect. Easy background images. Easy menu building in the config file. Grub understood enough of the filesystem to avoid the LILO cruft.

Now there seems to be about 5 layers of indirection, autodetection, probing, and shell scripting hacks to generate scripts that will eventually spit out a mess of obfuscated grub config files, and god forbid you touch any of this mess because any changes you make will be overwritten (a) next boot, (b) next time the scripts decide to update the config, (c) next system update, or (d) just whenever. All of this dynamic stuff to configure something that, for many systems, needs a config change about zero times per year.

← PreviousPage 4 of 5Next →