Software developer with over 10 years of experience across the entire stack of web applications. Very much a polyglot who's more on the "Product Engineer" side of full stack engineering. Looking for remote or hybrid roles.
That doesn't seem right. Looked up the rates for San Mateo and San Francisco county rates[1] and they're both under $0.400/kWh. On the other hand my parents in San Diego are paying over $0.450/kWh with rates scheduled to go even higher in 2024.
Why is power so expensive in San Diego? Wiki tells me that most of San Diego is served by a separate utility (compared to SF bay area): San Diego Gas & Electric.
I don't know why, but both power and gasoline are even more expensive in San Diego than in the Bay Area or Los Angeles. My hunch is that SD is weirdly isolated from imports and hasn't kept up with very recent growth.
IMHO, if you're really set on improving your resume, a service is worth it. Use one for the cheapest option possible and run it a few times on your resume -- you'll see the patterns and things it looks for.
In general, it would be things like:
* Avoid repetitive action words - "Built systems, built software, built infrastructure..."
* Add numbers/metrics where you can: "Improved site performance by 20%+"
* Line items should not be over 2 lines
Aside from that, choose a _standard_ resume format/layout. Don't get fancy with columns, colors, etc.
As for someone looking for a new position, I can give you anecdotal evidence.
A little background: I have 10+ years of professional experience. Polyglot. Experience with extremely small to medium sized companies.
I re-used my previous resume, which did decently well around 2019 when I was looking for a new position, but with updated info for the newest position I had. Applied to a number positions that I was very qualified for -- crickets. This put me in a bad spot mentally, honestly, as it felt like signals that I'm just not "good enough" for fancy "big tech".
I then updated my resume layout to be more parseable (admittedly this is another variable), then signed up for a service that helps ATS-ify my resume. This involved adding numbers to certain line items, reduce repetition, honestly some good feedback in general. Immediate recruiter messages the next day.
I was extremely averse to using a service like this as it just felt "dirty" or was a sign of my personal ethics "giving in" to some sort of system. Honestly, I still kind of feel that way, but this is the game we play now. I know for a fact I've been auto-rejected from a number of roles that I was 100%+ qualified for because of my resume.
I used resumeworded.com. I believe I initially found it on this thread [1], which also has a few more suggestions. I think they'll end up being roughly the same -- don't remember why I ended up choosing Resume Worded.
I remember that as well. I thought that _was_ the internet since that was my first real exposure to home internet. Outside of that it was just my elementary school and the library. When services like NetZero and Juno came out, my mind was blown knowing that I didn't need to have the entire AOL ecosystem load up -- which could take a while with a 14.4k modem and a 133MHz(?) Pentium with 32MB RAM.
I once showed this off to a friend by minimizing the AOL window, opening a folder, and typing some domain into the location bar. Back then IE was intermingled with explorer enough that this opened the website inside the folder window! Thus proving the internet existed outside of AOL!
We also had similar discoveries of editing the HTML of the folder itself before discovering .html files for making websites.
Then again when we discovered how to make content go into horizontal columns with this magic called <table> and <td> ! The magic!
I recall using this method to bypass the strict filtering of my child-level AOL account. I could browse chat rooms and play games on websites I couldn’t access in the AOL browser via IE. Good times!
I was the exact same. My mind was blown when I realized you could connect to AOL and THEN open an internet browser and just be ONLINE! I spent way to long thinking AOL was the internet before I think I saw my cousin do this and it changed my world forever.
The vast majority of the time the answer is no. I've even had recruiters contact me assuming I was with a company I left 2 years ago -- a company that no longer exists.
I guess it depends on the state. A friend recently was hit and had their car only slightly damaged. They went to insurance car shops that insurance recommended, but they all declined to fix the car. They ended up getting paid out and fixed it themselves since they're already skilled with maintaining vehicles, and they pocketed the rest.
In the US, firstly it is considered unfashionable by many to buy a used car altogether ("you're just buying someone else's problems!") and secondly, the only thing that can reliably affect resale value is if it condemned with a "salvage title." Which can mean a few things but usually means the car suffered more damage than it is economical to fix. But just the fact that a car was in a collision or had a claim against it does not automatically affect the car's future insurance rates or resale value.
We have a company called CarFax that produces vehicle history reports for used cars, but there are many problems with it. Starting with the fact that all reports are voluntary. I have looked at cars that were clearly in floods when you know what to look for and yet the CarFax was squeaky clean.
> But just the fact that a car was in a collision or had a claim against it does not automatically affect the car's ... resale value.
What? Accidents, even after repair, decrease the resale value of a car, significantly in the case of a young or exotic car, less so for an older, more pedestrian car.
Having been in an accident removes some possible buyers from the pool. (Some buyers will not knowingly buy a car with damage history.) That necessarily changes the balance of supply and demand for that car.
If you had a choice between buying a car that was in a crash and repaired versus the otherwise identically equipped car that had never been crashed, which would you choose? Lots of buyers prefer the latter option, which is why they're worth more than the former option.
I'm saying that accidents (depending on the severity) do not necessarily decrease the resale value of the car. You're saying that a car in an accident has a smaller pool or buyers. These can both be true.
There are two ways to sell a sub-prime car: 1) lower the price, and 2) wait for a less-than-diligent buyer to come along. Many private sellers and dealerships are perfectly fine with #2.
Lots of people do not know how to check for unreported previous damage to a car, and lots of people do not care if the car was in an accident as long as it was repaired, has no obvious damage, drives just fine, and has a green title. These are the people who eventually buy those cars.
The majority of cars sold are used cars. Yes there are some who won't consider a used car, but they are a minority (a large minority, but still a minority). The average car last 12 years, the typical new car is replaced every 3 years with a newer one.
A salvage title is only used when someone intends to restore the car, and then it goes back to a normal title once restored (or at least that is how my state did it 15 years ago - each state is different). You get the salvage title only to justify paying taxes on the actual value of the car (sales tax on a car is for actual value not the price you paid, so a salvage title is useful to prove it isn't worth what the book says) It will show up on CarFax as restored then. (though as you note most such issues never get a salvage title as they are not sold)
Don’t know what state or country you are in, but that isn’t the way a salvage title works in any US state that I am aware of.
A car with a salvage title stays branded with “rebuilt” or “restored” in all common scenarios. There are ways to wash them to unbranded, but most are unethical and involve retitling in different states and such, rather than simply restoring the car.
Regardless, unless dealing directly with the DMV, most people call a branded title a salvage title, or at least say something like, “the title isn’t clean”.
Salvage titles are restored wrecks. Back in the day when it was easy to get clean titles, people would steal cars and “restore” wrecks… or move parts from wrecks into stolen cars to launder them.
If you're going back and forth everyday, I would ignore every suggestion to stay outside SF, except for maybe stays in the Daly City-adjacent areas since more trains run through there. I travel to the Bay Area on occasion for work (and used to live there for a few years), the travel time + BART costs wouldn't be worth it IMO.
In terms of "Hacker houses", I've only known one person (a coworker) who stayed in one long-term, but he was pretty eccentric. He complained about his living situation a good amount, but, attempting to reduce some of his biases, they seem to be in a "you pay for what you get" type of situation.
Last suggestion: book an initial stay through a hotel/Airbnb with a short duration -- with the intent of finding a co-living space if you're really that intent on living in one. This will give you time to scope locations out _in person_ and potentially toss out options that only look good in advertisements.
Sorry, no idea about the logistics of them, but after a quick search: looking at Hacknsleep, they have a line that says "Move-in within days", so probably quick?
I don't think your arguments accurately cover the OP's argument at all. The key distinction is literally the first sentence: "Social media businesses should not charge* for APIs."
If you have a community [whatever] service that would not be a business. If you have a blog, that's could potentially be a very business-adjacent, but I'd argue it doesn't cover the "social media" qualification, so that also doesn't apply.
If you run a business and much of your content is user-generated (because it's a social media site), the OP is arguing that API access should be free/at cost.
> OP is arguing that API access should be free/at cost.
Implicitly he is also arguing that it must exist at all.
But let's consider further your own commercial clause. Apple has a discussion board for their support community [1] - and now we are mandating that Apple must both have an API for users to access it and must only charge cost. Who gets to determine the cost? Is it hardware costs? Does it include R&D? Is there a fixed margin set by a regulator?
The grey area on this is as wide as an ocean. But I do think it is a little funny that people are arguing about this like it is equivalent to a universal human right.
A server-rendered HTML website is an API. If said HTML website is unauthenticated and freely accessible by any user-agent, then it's a de-facto public API, too. This is the case for the Apple discussion boards. You don't have to authenticate with their backend before scraping anything you'd like off of the site. You can build third-party tools to read or even interact with this site, by scraping the HTML.
This thing with Reddit is only the big deal that it is, because Reddit's backend blocks "app" user-agents from simply scraping pages from the non-authenticated Reddit HTML website. (If this wasn't true, they'd just do that, and none of this would be an issue.) But these third-party UAs are instead forced to go through the authenticated data API — where they can then be API-credit-limited and forced into paid data-API subscription plans.
I think a more reasonable argument could be “If a site provides an API for fetching user-generated content, it should be free”. (But just as a moral argument, not something to be enforced with regulations.) The issue is that if they provide a paid API for users’ content, they acknowledge the value in the content provided by their users (whom they already have to thank for all their ad revenue), so it seems unjust for them to suddenly start selling that content, especially without sharing the API revenue with the content creators or something.
* Remote: Yes, open to hybrid
* Willing to relocate: Yes. Mainly San Francisco/Bay Area and Seattle areas, but will consider others as well.
* Technologies: * Languages: Javascript/Typescript, Python, Java, C#/.NET, PHP * Backend: Node.js, Express/koa/etc., Django, Flask, FastAPI, Quarkus, Laravel, Symfony * Frontend: React, Vue.js, Ember.js, Svelte, Solid.js, Angular, Tailwind CSS, Bootstrap * Databases: SQL, PostgreSQL, MySQL * Tooling: GraphQL, git, Ansible, Docker, Kubernetes
* Résumé/CV: https://www.linkedin.com/in/allan-almazan-63379295/
* GitHub: https://github.com/aalmazan/
Software developer with over 10 years of experience across the entire stack of web applications. Very much a polyglot who's more on the "Product Engineer" side of full stack engineering. Looking for remote or hybrid roles.