« Bonjour, comment êtes-vous? » barely translates to « Hi, how are you feeling today? » or, depending on the context, to something like « Hi, please describe yourself » to a native French speaker.

Former employee here, can’t recommend Datadog enough, loved my 4 years there!

Hey do you have a recruiter email I could reach out to?

You'd probably want to take a look at https://gitpay.me/ or https://www.bountysource.com/

Both of the platforms seem pretty inactive, but I can try - thanks!

I can't thank you enough for this comment, it's exactly what I was looking for for so long.

Correct me if I'm wrong but I use "FIXME" for this intent. I keep TODO for stuff actually left to implement.

To me, FIX implies that something is wrong, not that it works but could use improvement.

I would like to have a tag for "here's something that works, but could be improved" though!

Pray tell, what line would you NOT put that tag on? That's like, all code...

TODO is for when you know something specific that can be improved and want to document it, not just generally that nothing is perfect.

I occasionally get to write code that is as good as I think it can be. That doesn’t mean it’s perfect, but I don’t know how to improve it.

Something I've seen Jonathan Blow do that I like is tag things // @Speed when doing a quick to type but slow to run kind of first pass.

It seems nice to have tags for places to jump where the improvements are obvious, rather than hoping to just remember/spot them later.

I think we all occasionally write code we like, but I also write code I don't like, but only the most vague idea on how to improve.

I similarly don't want to brag about my skills in pointing out areas of improvement in code that others might think is optimal, so I won't answer that.

Isn't that what NOTE is for? The code is fine for now, but here are some constrains/limitations/implementation details that you should know when you want to touch that par of the code.

That seems like a good compromise. I've used LOOKAT to note places where I got things going but felt like there was a better way of doing things if I had more time.

Is there a standard for valid flags? I recently recommended a client use `TODOSECURITY` for todos which had security implications until fixed - I discovered functionality which was implemented before authorisation had been developed, resulting in a codepath which was unintentionally reachable by standard users.

Seemed weird to make up a codeword but I wasn't aware of any standard convention, and visually highlighting high impact issues (w/ the bonus of greppability) seemed like a sane approach in rapid development environments.

Open a ticket for that straight away and start working on it immediately. Or 3 years later. Whichever actually happens.

Yeah, that's probably true. I don't have any visibility over that particular projects ticketing system but I imagine it was never raised given it wasn't fixed until I noticed it.

I’d strongly recommend not landing code that has known security problems.

It was my job to look for security problems.

It was founded in NYC

https://en.wikipedia.org/wiki/Datadog#History

> Want to port a SIM? I'll put your request in now but it will wait for 5 business days before it happens, and at any point if you or someone claiming to be you calls up to stop it, we stop it, no questions asked.

Funny because that's exactly what happens in France when you do so. I must have sounded a bit dumb when I asked when my number would be active when I changed from Tello to Verizon. I couldn't believe it was effective right away.

It's been a while since I ported a number but the last time I did it took days here in the UK too. I just assumed it was typical inefficiency by the mobile operators rather than a security thing, however.

It takes days in the UK because we have a crappy system where instead of having a central register of number -> provider, calls are still routed to a ported number via the "donor" network, i.e. the network the number range belongs. So I just ported from O2 to EE, and my calls and texts will still go through o2, and then sent on to EE. Not very efficient.

You can download the PDFs and look at the table of contents if you'd like

Yes, doing that now. :)

I don't see nets? https://news.developer.nvidia.com/wp-content/uploads/2019/04...

It's really different from rugby.

the gates are nets. It's not really that different. You pass the same, they even name the kicks the same (grubber, and drop kick) and it uses a rugby ball.

Same for iOS, fyi.

Ah true, I forget on my iPad I installed an alternative keyboard. I said Android cause I have more experience using Android. I sort of stopped using my iPad once I bought a Surface Book 2. Since it has a Netflix / Hulu app I dont need my iPad as much anymore.