sonofgod

Depends on the task, but if your task is amenable to it, I'd consider writing tests which basically say, at a very high level: "Is the output for a given set of inputs the same?"

Even if you're wrapping the entire application.

We're not looking for "does this code do the right thing", just "does this code do the same thing" (as the initial code).

At which point you'll at least have some more confidence that you aren't damaging the codebase due to having not understood a part of it.

Sometimes the spreadsheets are the output of one system, but the input to the next: the spreadsheets of the Office of National Statistics in the UK are the final, and official output of a long chain of number wrangling, but when it comes to re-consuming them to power their new data-driven website it's a real challenge -- I wound up working on a project to allow programmatic consumption of these complex spreadsheets.

(https://github.com/sensiblecodeio/databaker for the top-level project; https://github.com/sensiblecodeio/xypath for the library I created).

Get in touch if you're interested -- dave.mckee@gmail.com

Whilst there's a few hashing algorithms explicitly designed to be memory and time-intensive to make password retrieval impractical, most are really fast, even in Javascript. (Given there's g and so should be fine but isn't particularly lightweight. oing to be network access, I expect it to be entirely negligible)

In terms of performance I was more wondering whether or not "£" (one code point, two bytes) was much less expensive than "Ao" (two code points, two bytes). Just restricting yourself to ASCII might also have advantages for ensuring portability.

https://qntm.org/safe might also be of interest: discusses potential issues with using unicode as a high-density encoding -- base-2048 is Twitter-safe.

Instead of addition, why not use an actual hashing algorithm, truncated to a certain number of bits? That'll give you better binning and give you flexibility about filesize / number of file tradeoffs.

I like the idea of using unicode characters -- have you performance tested it to see if it gives superior performance to an ASCII filename of the same number of bytes?

What is the weight of an object of mass 5 kg

98N (Confidence: 49.05%)

If we multiply the answer by the confidence, we're pretty close...

An additional belief I have been disabused of:

> Excel will load valid CSV files correctly. If a field contains more than 32kb of text , Excel will continue outputting that text into the next cell, and it won't be quoted, so the CSV file appears to be flooded with complete garbage from that point on.

Oh, and searches for "revolvor" and "gu n" work just fine. So only people with bad spelling will be able to buy guns...

Also "ar 15", unsuprisingly.

~/valvedev/hl3

There is literally no useful information on this website.

Posting this on Hacker News is probably counterproductive to your goals.

Text surrounded by asterisks is italicized, if the character after the first asterisk isn't whitespace.

Text after a blank line that is indented by two or more spaces is reproduced verbatim. (This is intended for code.)

https://news.ycombinator.com/formatdoc

italic

  code block
  :)

Wondering how long it'll be before we have `curl ... | cmd` as standard installation instructions on Windows.

(Probably a while: command line familiarity is far from a given in Windows)

Does the author actually define surprising anywhere other than "George Shackle's definition"?

Not even the first time this specific blogspam has been posted by OP.

Yep. requests.session fixes the vast majority of cookie / login / session / problems. Replaying the same headers is also a powerful technique, so long as they aren't constantly changing.

ASPX is still horrid, but just about doable if you pull all the hidden form variables out of the HTML and put them back into the header verbatim. But you're probably best off going down a headless browser route at that point.

If anyone's wanting someone with scraping experience (UK/remote), I'm currently available... (dave.mckee@gmail.com)

I'd call my graphics app "... Pro" just to riff off Paint Shop Pro.

This may show my age.

If there's someone from Datalogue --

It's really hard to work out where you're based; I'm guessing New York from a tag on one of your medium posts. This is usually important to be able to discover when you're recruiting!

There's no way to get in touch with you that isn't "we'll contact you" with a mandatory phone number (which you're not getting).

I was initially interested in applying but now I'm not.

If you are about, could you let us know how well Open Source Interviewing has worked for you in the past? Or is this the first time you've done it?

It's a terrible idea, but an excellent example of experience:

https://github.com/nvbn/thefuck

[TL;DR -- typo a command, type 'fuck', will run the command you should have run]

A friend claims to have fictitiously added the fact that he went to Durham University to Wikipedia approximately a decade ago; and that other sources have used Wikipedia as a source of that information.

And now we'll never know for certain.

$55k, now. https://twitter.com/actual_ransom/

And <script>alert("!")</script> works :)

This isn't newsworthy. I'd suggest trying at stackoverflow, but your question isn't particularly well formed to start with.

Which stage of the tutorial are you at?

Quickly googling the error message gives https://ubuntuforums.org/showthread.php?t=1654068 which suggests it might be caused by conflicting / missing apt repositories.

Good luck.

I'm getting some sort of resource allocation error, I think it's requesting that I get fucked, but it has no more fucks to give.

:P

If I were your fellow dev I'd be mildly annoyed that the setbacks meant you couldn't see launch, and we couldn't celebrate with you, so long as I understood that your hands were tied. You tried to see it through, but circumstances dictated otherwise. Communication is key.

As the new employer, I'd be distinctly annoyed if you pushed back a week; they're probably counting on you and starting to schedule new starter stuff. That could colour an entire working relationship badly.

Good luck with the new job!

One additional character may be for "I fatfingered a key as I pressed Enter".

You don't need to store a second hash for any of these; just transform the sent password with (invert all characters, invert one character, delete last character), rehash it and compare it to correct.

Whilst it does increase the numerator, it also allows Facebook to decrease the number of obviously wrong password attempts permitted before taking additional precautions. Since these are overwhelmingly likely to be user error, I think it's a perfectly reasonable tradeoff.

No splash screen. Just show me the web app already, and maybe tell me there's an app on the webapp page. :P

If you're wanting to explore the history of messaging, olduse.net has a 30-year delayed live newsfeed...

Mostly I learnt that just about nothing has changed...

Don't use this if you're ever going to type in a password where the screen might be shared -- the constantly-updating "is my password correct" glyphs give away enough information to make it super trivial to decode by eye.

PS: the password for the demonstration gif is "passwordpassword"

They're likely to also be https://github.com/alpeb who also works with Scala and there are contact details there.