orib

Clipp | Sr Back-end Tech Lead | NYC | https://getclipp.com

Clipp’s vision is to digitize the food supply chain, starting with the $325 billion U.S. food ingredient distribution industry.

We’re seeking a Tech Lead with a strong focus on backend development and infrastructure to join our small but passionate team. You will play a pivotal role in building and scaling the Clipp platform, working closely with the cofounders to drive both technical and strategic initiatives.

Experience:

* 7+ years of software engineering experience, with 3+ years in a team lead role

* Hands-on experience building SaaS platforms, with a deep understanding of backend development and infrastructure.

* Experience utilizing Agile methodology to deliver complex software projects.

Technical Skills

* Proficiency in NodeJS, TypeScript, AWS, REST, GraphQL, infrastructure-as-code and containerization tools such as Docker and Kubernetes.

Bonus Points:

* Background in e-commerce or the restaurant industry.

* Experience working with payment processing providers.

To apply, reach out to ori@orib.dev, and I'll pass you along.

Great insights about improving the rust compiler performance! What else would you do to speed it up?

There's one quote that I see people refer to quite often:

William Roper: So, now you give the Devil the benefit of law!

Sir Thomas More: Yes! What would you do? Cut a great road through the law to get after the Devil?

William Roper: Yes, I'd cut down every law in England to do that!

Sir Thomas More: Oh? And when the last law was down, and the Devil turned 'round on you, where would you hide, Roper, the laws all being flat? This country is planted thick with laws, from coast to coast, Man's laws, not God's! And if you cut them down, and you're just the man to do it, do you really think you could stand upright in the winds that would blow then? Yes, I'd give the Devil benefit of law, for my own safety's sake!

  -- A Man for All Seasons, 1966.

Short patent lifetimes. Long enough for you to get out and establish yourself in the market, but short enough that it wouldn't kill a competitor to wait a bit. It would also dramatically reduce the cost of licensing a patent since the waiting time for it to expire would drop so much.

Perhaps a good amount of time would be one or two years?

I still think asm is essential to know. And I'm not even an old fart. Knowing assembly makes it far easier to rationalize about what my C programs are doing, how things will perform, what the machine actually does, and so on, even up into my Ocaml code (which is what I tend to work in for much of my code these days).

Even C doesn't teach you about cache behavior, register spilling, calling conventions, and so on.

Plus, it helps to know assembly massively when you're in the embedded domain, or whenever you're close to the metal.

Allow any email address.

I'm at mcmaster, which has a mcmaster.ca address. I don't think it's possible to match on email address to allow all schools, so just ask for the school that someone attends. If you let some non-students through, what does it matter?

Answer: It's far easier to talk to someone over a beer when you're in the same building as them. Or to pop up at their office unplanned with a question. Or to work on a project with team members.

School isn't all about lectures, and even for lectures, pre-recorded lectures don't let you ask questions.

Yes, I'm familiar. I was playing with double meanings ;-)

Minitrue? You mean Minimal Truth?

Then don't do web-apps. There's nothing wrong with starting doing GUI apps with PyGame or something

It might be a good read if it actually talked about what happened in the book. However, it didn't.

Does everything have to turn a profit? No.

Does everything that you're trying to earn a living off of, pay bills with, and hire employees with have to turn a profit? Hell yes.

If you're not going to aim at providing a return on investment, don't pretend you're a business.

As four bars wrapped in a poster, with pins (or glue) to put it together, perhaps?

At least on this site, it sounds like any startup would be preferred to any established company including google. Although that really does seem to be mostly the tone of this site.

I remember this design from my childhood. (Well, a variation of it). Dropping the tail and tearing elevators/ailerons into the back of it turns it into an awesome stunt plane, one that can do loops and so on beautifully, or can (if thrown right) come back to you like a boomerang.

It seems that when you're asked for a plane, you're expected to create a plane, not a wad of paper.

Presumably, this was during a unit on areodynamics, and the idea was to demonstrate an understanding of areodynamics, and not to show that you can throw balls farther than you can throw planes.

If the teacher had asked for the object that would go farthest, instead of specifically asking for a paper plane, then you would have a point.

On Linux, left+right click emulate a middle click, at least if you only have two buttons.

With RSA private keys, users don't see or manipulate them directly (usually). With a private-key based security system, most users would go "Huh? what's a private key?" if you asked them to send it.

With biometrics, you can't send them over a phone or over the internet.

Social engineering will always be a problem, but passwords are far easier to obtain with social engineering. Biometrics and so on reduce the number of attack vectors.

They can and do, for the most part. iPhone knockoffs are a dime a dozen, for the most part, although Apple has design patents to keep them from looking too close to they original.

Or maybe they were aware of it in the good old times too, and they think it was crap then too?

I have no patience for working on lame assignments, and my marks suffer, but I still have no patience for people who are in school hoping to coast through. If you don't challenge yourself, you're wasting everyone's time.

If you can determine an upper bound on n, then your algorithm is technically O(1), and you don't have to worry about scaling.

If you want to be able to handle any value of n, and expect it to be large, you should care about O(n^2) algorithms. You don't have to necessarily get rid of them all at once, but you should at least know where they exist and have them listed as possible pain points or places to start optimizing.

Sure, but some things (eg, surround.vim) can't be emulated with that.

I'm reminded of Carl Worth's effort to port the HG guide to Git. It was mostly a search-replace effort, where the concepts were more or less the same, and the commands were similar.

One interesting point to note it is certainly not an issue to sell the source to your program in a bundle with the binaries, allowing enterprising hackers to modify and update the software. You could even allow distribution of these changes.

Allowing this doesn't mean that you are forced to give up copyright on the source, or release it under an open source license. A license that says "You may have, modify, and distribute modifications to the source, but not duplicate or redistribute it" is certainly something that I would find interesting, and would love to see more software released under.

Argh! I wish there was an un-downmod button. I hate it when I accidentally miss and downmmod instead of upmod.

It's a less archaic way of saying "one". 'when one does X' vs 'when you do x'

what was your point then, if not that programmers won't need to know concurrency because it will be in black boxes that they haven't written? (Bear with me, I'm a bit dense at the moment. I haven't had much sleep the last while)

I still think that programmers that are actually doing more than simply gluing together premade libraries will need to be familiar with concurrency, and that anyone taking a theoretical computer science degree to graduate and glue together libraries is probably overqualified.

No, but I consider a chip maker telling me what kind of chips they're going to be making legit. Especially when all the other chip makers are saying the same thing (All the other chip makers: AMD, Freescale, Intel, Sun, Marvell, and others)

"Sorry, but I don't buy that. We're also moving to a thin client world where we don't actually need that much power on our thin clients."

Yeah, we've heard it before, several times, from the moment that networking was invented and onwards. Why will the push for this stick _this_ time around?

From what I've seen helping people I know handle pointers, they're really actually having trouble with the concepts of pointers. Getting them to draw the box diagrams with pointers correctly is challenging. The notation is an extra challenge, but it's not the main difficulty.

It's not the notation, it is the concept.