dmlittle

I currently run this! Kinda... I haven't really touched it since 2017 when I built it as an evening project to see if it could be done as a static AWS API Gateway configuration. It costs a few dollars a month plus the domain cost and a fair amount of people use it so I've kept it up and running.

I've been meaning on writing the same functionality as an actual application and adding things like custom response timers, timeouts and more and deploying it to fly.io to try their service out but I haven't gotten around to doing it yet.

Lichess - https://lichess.org/

> what if my team complained that I wasn’t doing any work? Regardless of whether you're an incoming manager or senior IC, it's a good idea to observe your first few weeks/couple of months in a new team rather than come in suggesting big changes[1]. Yes, things might not be in an ideal situation, but there might be context you're missing which explains why things are the way they are.

[1] There a few times where big, shocking changes are necessary to reset a team in a bad situation. Most of the time this is not the case.

I think the users started calling them “servers” and it stuck. Their API, and I’m guessing internal naming as well, calls them guilds[1]

[1] https://discord.com/developers/docs/resources/guild

The design looks like a crossover between the Financial Times and Increment[0] (which is published by Stripe).

[0] https://increment.com/

A service oriented architecture is not a bad thing. It has its benefits as well as it’s downsides. The key is to know when to use the pattern and when not to.

I’m not sure what exactly “modular monolith” means but I’m guessing it’s some kind of mono repo with different services that share a large core but can scale independently. At Shopify’s scale I doubt you can just use a single service and database and not run into problems (both technical and development productivity wise).

I think it depends on your pricing model. If you’re paying 5-10% for a CRM/specialized app/integration you’re likely charging too little. I’ve had bills be around 1-2% and that was willingly knowing I wasn’t optimizing for billing but rather development productivity. I could have cut the costs to under 1% but it wasn’t worth the effort vs. building net new functionality.

I believe the extra yearly fee is to offset the tax on gas used to maintain road infrastructure that all vehicles use.

I have minimal (almost zero) experience with Google Cloud but if were to guess the reason to not consider Cloud Run is the pricing model. While solutions like Cloud Run (and Lambda or Fargate in AWS) give you a lot of flexibility they are significantly more expensive than orchestrating servers and services yourself. At a small scale the increase pricing is worth it for flexibility but there's definitely a point at which it switches and it's too expensive and not worth it anymore. From the blog post it seems they have a sustained average of 30,000 requests per second which probably puts them in the category where rolling it themselves is financially worth it.

Comparing Cloud Run pricing with VMs and Preemptible VMs you can see why. I'm going to ignore networking bandwidth costs as I assume (maybe incorrectly) that they're the same across Google Cloud services. That leaves us with CPU, Memory and Requests pricing.

CPU Pricing:

Cloud Run: $0.00002400 per vCPU-second [1]

On-demand VM: $0.00000605861 per vCPU-second ($0.021811 / vCPU hour) (~75% cheaper vs. Cloud Run) [2]

Preemptible VM: $0.0000018175 per vCPU-second($0.006543 / vCPU hour) (~92% cheaper vs. Cloud Run) [2]

Memory Pricing:

Cloud Run: $0.00000250 per GiB-Second [1]

On-demand VM: $0.00000081194 per GiB-second ($0.002923 / GB hour) (~67% cheaper vs. Cloud Run) [2]

Preemptible VM: $0.0000002436 per GiB-second($0.000877 / GB hour) (~90% cheaper vs. Cloud Run) [2]

Requests Pricing:

This is complicated since Cloud Run charges per request ($0.40 per million requests[1]) which would put them at roughly $378,000 per year (at a 30k request per second average). Load balancers charge per hour and per bandwidth (regardless of traffic of which they have it sustained) at $0.025 per hour per proxy instance and $0.008 per GB of data transfer[3]. I'm not sure how it compares but I'm sure it's much on an averaged our per request basis.

Looking at the CPU and Memory alone you can see the price differential and why it might not be worth it when you're paying hundred of thousands of dollars per month in infrastructure per year (they might spending much more but at this scale it is when its starts to matter). Assuming a middle ground somewhere in the 80% savings using on-demand and preemptibles vs. cloud run at low costs you're talking about $60/mo vs $300/mo respectively but once you're in the $50,000/mo range you're talking about the difference between $50,000/mo using on-demand/preemptibles vs $250,000/mo on Cloud Run.

[1] https://cloud.google.com/run#section-14 [2] https://cloud.google.com/compute/vm-instance-pricing#general... [3] https://cloud.google.com/vpc/network-pricing#lb

It also depends on traffic patterns. For EC2 you're paying per hour regardless of whether you had traffic or not. For Lambda you're paying per unit of time used and you pay nothing when the function isn't invoked.

You pretty much copy pasted the Tailwind UI license word for word and replaced a few Tailwind UI-specific words with yours.

Components => download files

Tailwind UI components => FlowBite elements

Tailwind Labs Inc. => Crafty Dwarf LLC

Tailwind UI License: https://tailwindui.com/license

Flowbite License: https://flowbite.com/license/

Slightly off-topic answer: back in the day these used to be Java Applets so the original mathlets name is probably a pun on them.

Not these ones in particular but a very common set of illustrations comes from unDraw.

https://undraw.co/illustrations

From the repo:

> Disclaimer

> The service at https://transfersh.com is of unknown origin and reported as cloud malware.

AB No.168[1], specifically 432.3(c)

(c) An employer, upon reasonable request, shall provide the pay scale for a position to an applicant applying for employment.

[1] https://leginfo.legislature.ca.gov/faces/billNavClient.xhtml...

In California recruiters are legally obligated to disclose the salary range upon request.

Historically I've used bisect on codebases I wasn't familiar with knew there was a regression I was trying to fix. If you can automate your regression testing with a script git bisect is really powerful and will save you _a lot of time_. Although if it's easy to test given the logarithmic nature of bisect maybe writing the script might not be worth the time.

As someone who recently interviewed (although not at Facebook) the number is the _annual compensation package at the time they signed their offer_ (it includes base salary + annual stock grant + bonus). If someone got $1,000,000 in annual compensation 2 years ago, the stock portion per year will likely be larger now due to appreciation of the stock. These numbers are crazy high and before I interviewed this time around I was somewhat skeptic of how real these numbers were outside of a few outliers but now I'm pretty sure it's pretty common.

Ive never had a good experience with whiteboard paint. The walls are not smooth so you always leave some residue when removing the ink. Over time it becomes pretty noticeable unless you spend a significant amount of elbow grease cleaning it.

It all depends on your use case. If your input is bound to a small N, I’ll take the simplest to understand implementation regardless of algorithmic complexity. Future you and other people will thank you later.

I think it depends on what you’re doing. The author of the the Reddit post mentioned he’s primarily working with data systems. I can see the appeal of someone running quick, ephemeral data analysis not wanting to deal with static typing. But for long term use cases the static typing guard rails is definitely nice.

I’m not sure if all natural immunities are stronger, or even strong. I’m not denying those exists but I also personally know 3 people that have gotten COVID-19 twice.

If natural immunity only protects against a particular strain and the vaccine against a group of them I think that’s still a solid reason to continue pushing for people to get vaccinated.

Most likely not. WWDC is for software announcements, mainly the new iOS and macOS versions, and I don't believe new hardware has even been presented (this is not true, see edit).

EDIT: I was wrong an hardware has indeed been presented at WWDC before. I still believe, however, that a new M1 16" MacBook Pro isn't a WWDC-worthy announcement and will likely be announced in October.

FWIW you can add HTTP Basic Auth information in URL links and all major browsers and other HTTP clients (for the most part) should interpret it correctly.

https://:[API_KEY]@v6.exchangerate-api.com/v6/latest/USD

If you only have an API key and not a token (username) and secret (password) I recommend passing the API key as a password as some logging solutions do log the basic auth username in the data recorded.

The problem with having your API key in the URL is that they'll likely be logged all over the place when they're meant to be secret. You probably have the keys being leaked in logs, error reports, metrics, etc.

Convox[1] is another one

[1] https://convox.com/

Are you looking for technical papers on how they work or practical blog posts on what you can do with them?

For both Bitcoin and Etherium the original white papers do not paint a full picture of the state of each cryptocurrency. Here are a few links I recently read on both BTC and ETH:

Bitcoin Wiki: https://en.bitcoin.it/wiki/Main_Page

Bitcoin BIPs: https://github.com/bitcoin/bips

Etherium Website: https://ethereum.org/ (it has a lot of information spread all over it)

ETH2 Beacon Chain Blog Post: https://ethos.dev/beacon-chain/

There's a lot more literature that you can find via Google but it's spread out all over the place.

Gitlab used to have their geographic location factors public. They're no longer public but here's how it looked before they made it private: https://gitlab.com/gitlab-com/www-gitlab-com/-/blob/e7e3aeff...

From talking to friends that work at different companies there's also been a movement to simplify geographic location pay to be around 5% to 15% less than HCOL cities for the rest of the US or simply have no localization factors at all.

The reason why it doesn't exist is licensing and a bunch of regulatory processing that needs to be done to keep the license.

Lob, as a mail provider, built and licenses this from the USPS for its mail operations but is unable to sell it to customers due to licensing and regulatory issues. Similarly, SmartyStreets used to sell this service but discontinued it due to the amount of regulatory and reporting work that was required to keep the licensing rights.

Source: I used to work at Lob and helped build those systems.

There are a lot of licensing restrictions that will make it extremely hard, if not impossible, for you to buy this from a third-party vendor. You'll need to sign a PAF(https://postalpro.usps.com/NCOALink_PAF) with the NCOA service provider and if I remember correctly the smallest "batch" of addresses that the licensee can run at a time is of 100. The service provider also cannot run addresses via NCOA without actually sending a piece of mail to the address being processed.

Source: I helped build a USPS CASS-certified address verification and NCOA API at my previous employer. Dealing with USPS licensing was a PITA.