Now you have to specify whether or not it’s moved during queries (and what if it moves again?) There’s probably a more elegant way I’m not thinking of, but standard created_at and updated_at fields would work: if a given date is <= the move date, it’s the original airport, else the new one. Rinse and repeat if it moves again.
> It’s so toxic that the poison from a single newt can easily kill several adult humans. You could literally die from licking this newt, just once.
TBF there is one death reported in Oregon from someone eating an entire newt in 1979, but they aren’t as bad as the article would have you believe. Many of us have handled these newts. There would be a lot more dead people if licking is all it took.
> A 29-year-old man drank approximately 150 mL of whiskey at about 11 AM July 9, 1979. At 6 PM he swallowed a 20-cm newt on a dare. Within ten minutes he complained of tingling of the lips. During the next two hours he began complaining of numbness and weakness and stated that he thought he was going to die. He refused to be transported to a hospital and was left alone for 15 minutes and then experienced cardiopulmonary arrest
Wow how many reverse geocode requests does a google API key make to get a bill into the thousands!?
Maybe a good iteration of this is use the .01 accuracy line work for the 99.9% of users but anything within 100m of a border could be sent to google API to get the edge cases. Probably would be in the free tier.
Yeah I wonder if maybe they weren’t caching the responses locally and repeatedly sending their requests to Google. I run a site which gets 1.5M unique visitors a month and we use Google geocoding api, and it comes out to $0/month, because our usage fits in their free tier.
I absolutely completely agree and do this myself. Unfortunately all of my peers and bosses don’t see the value, and the shop is overrun with trend chasing resume driven developers. React/node/next hosting on aws and containers and it will all be out of date next year. Everything we do has such low amount of users we don’t need anything but a single VPS and simple backend. Many of my apps from 10 years ago still run the same rails and jQuery just fine. Actually upgrading the rails versions and pulling out the jQuery dependencies is easy now too. It’s just so much simpler and works perfectly. But this is seen as detrimental to my career. It’s not appreciated. I sound like a dinosaur to the bosses and coworkers. But I enjoy it and my shit works fine. I’m saving so much time and hosting costs. Everything runs on a $40 VPS.
The point of your opponent's argument is that measured age should be an indicator of maturity and stability of frameworks and toolchains.
In JavaScript, it is not. So you claiming 10 years as a time frame in your response is in bad faith, because you certainly know that code written 10 years ago is 100% incompatible with the modern versions of the same frameworks.
This is the case at many teams in almost all companies. One sad reality is people want to keep their jobs and so they tend to inflate stacks and codebases so much so that they can "keep working on things" for a long long time.
Sorry to hear your situation but I found there's hardly any point in debating with your team on moving towards simplicity - just better to keep your head down and take that paycheck every 2 weeks.
My goal is to build a microstartup with a small team - and for that I am definitely going to choose the traditional JQuery/HTMX/Turbo setup with a server that renders templates. To hell with React.
I understand your perspective. It's similar to AWS services like CloudFront, API Gateway, SQS, and Lambdas—all designed for a microservice architecture that may not be necessary if scaling isn't a priority. The same applies to frameworks and libraries such as Next.js, and even React, Vue, or Angular, in my opinion. Most products and companies are not on the scale of Netflix, Spotify, or Facebook.
This leads me to question why people still use jQuery instead of native JavaScript. From my understanding, jQuery primarily serves as a polyfill.
So why jQuery and not native Javascript?
> This leads me to question why people still use jQuery instead of native JavaScript.
Most cases because it is not worth the refactoring to remove jQuery and in a few cases when it is in new project is because the person coding doesn't know to code without it.
You are right that you are being efficient and reasonable, but also you are right that you sound like a dinosaur. This is the same for people who cling to C as "this is all I need", possibly producing beautiful efficient code with no VMs or slow interpreters, at the cost of lower cooperation with their colleagues.
The bottom line is your choice of tools is also a social thing. Rejecting the mainstream tooling can be appreciated by some, confuse others, and sadly developers with lower self confidence might even see it as a form of insult.
> You are right that you are being efficient and reasonable
Well, that’s all I needed to hear. What’s the point of not sounding old-fashioned when the new fashion is worse? Considering the social point, why not be more critical when the efficient and reasonable thing is derided by others as old-fashioned? Why not expect those people to update their world view?
I think you’ll meet most of the community and could gain some standing working at the town gas station actually, especially if you try to be even a little bit friendly with the locals.
This is awesome, thanks. I’m currently employed but this is nice to see what’s out there at a glance. How do you calculate/know the total compensation? Like the base pay matches the info in the Airbnb opportunity but the total compensation is nearly double the base pay range amount, but isn’t quantified in the posting itself.
Thank you for your kind words! I have this question on the faq page and am attaching the answer below:
4. Where are the salary data sourced from?
Tech companies typically structure salary, often called total compensation, into 3 parts: base salary, equity, and bonus.
Base salary is pulled directly from each job post, thanks to the U.S. Pay Transparency laws (e.g. California SB-1162 in 2011), which require companies to include salary ranges in job listings to help address wage gaps caused by bias or discrimination.
Total compensation is sourced from levels.fyi, a platform that collects leveling and salary info through crowdsourcing.
Unfortunately, current laws in many states, such as Washington RCW 49.58.110 in 2022, only require companies to provide base salary ranges along with a general description of other forms of compensation. This allows companies to omit equity and bonus details. Hopefully, future legislation will help close this gap.
It feels odd that Europe has taken so long to come up with equivalent pay transparency legislation (due 2026). And of course, it's an EU directive, which means in the UK we won't get it.
Wow, it was able to Dox me pretty good when I asked it analyze my comments and decide if I’m anyone else from the internet. I’m not trying to be anonymous but this is a good reminder it’s a tall order to be these days if you participate in any communities
Ah yes, and I watched all 29 minutes to find out. It was still very interesting though and I’m still impressed. Not sure what the terminal program they showed at the beginning was, but the thing only “plays doom” (theme song)
reply