Technologies: 10 years of professional experience, working primarily in full-stack web development. I work daily in Python, FastAPI, Ruby, Rails, Sinatra, MySQL, PostgreSQL, Linux, MacOS, Docker, AWS (EC2, RDS, Elastic Beanstalk, IAM), Git. I'm familiar (Use most months) with ElasticSearch, CloudSearch, Tailwind, Vue. As Hobbies, or smaller projects (used on at least one completed project over the past five years): Go, Zig, C, C++, Rust, Phoenix, NoSQL, MongoDB, (probably more, but these were the ones that came to mind.)
My day job has me performing two main functions:
- Building full stack web development systems. I generally lean more towards writing backend code, and documenting our infrastructure. UI is my weakest area. This role has me working in datasets with ~1 billion row tables, and search indexes with ~100 million documents. Since we're a small company (~8 developers), I have been a major part of the architecture of our systems over the past 8 years. We've got five separate core businesses that our dev team supports, and I've been a part of architecting and implementing all of them. I would prefer to focus more on backend development in a future role.
- Creating one-off scripts or processes to assist in business functions. These tend to involve quickly reverse engineering undocumented web APIs we have permission to use, and querying them for our customers. At their simplest, these are a mix of writing some SQL and a few HTTP requests. At their most complicated, they have involved designing and implementing a tree structure to accurately model the business domain, and then pulling data about these structures from relevant public APIs.
- Miscellaneous tasks as they come up, recently, I reduced the cost of a company's AWS CloudSearch spend by 80% (over 10k/month) by reviewing their codebase, doing some research, and improving what they were storing and how they were doing so. This required a one-line code change on the existing codebase, and writing a new, short (~500 line) indexer. Doing a deep dive into the single highest AWS line item was the impetus for the project, and frankly, it turned out far better than expected.
Outside of work, I ran https://www.thiswebsitewillselfdestruct.com, a website I built and maintain. It really will self-destruct, and it reaches ~100k users and handles ~13M requests each month. Building tools and infrastructure to manage its moderation and keep it a positive community has been a huge learning experience.
Deadlock is quite different to Valorant in key ways. Rather than Valorsnt, which is essentially Counterstrike with hero powers. deadlock is Valorant plus Dota2. There are creeps and base management and extensive items.
I certainly think Deadlocks ui is unfinished, but the gameplay is certainly something that hasn't been done super well.
I don't love deadlock yet but haven't played it much. Plus, my opinion means nothing, I thought Artifact was a great game.
I very much agree. I just want to provide some evidence of one if your points:
> if someone is interested in making video games I feel like they'd actually be a bit disappointed after a while of working at Valve.
In 2018, valve aquired Campo Santo. They were a 12 person company who made Firewatch and were working on a new game.
Since then, one of the founders worked on writing Half-Life Alyx. The rest have done little to nothing at valve despite being industry veterans who alwys seemed passionate about games. At least half of the employees at the time of the aquisition have left valve. Im too lazy and sick to look up everyone, but the people who wanted to make games left to good companies where they could work on games.
I personally am happy for the Campo Santo team that they hopefully did well financially in the acquisition, but I an sad that a team working on novel narrative games with high production values was disbanded with little to show for it.
When you filter by election cycle it looks like they aren’t making any huge donations compared to their baseline. Maybe the baseline donations stop things like this, but I don’t think I’d jump to that being the clear reason.
I'm hoping there is a better selling point than a really good home theater for single people. When I was single, having a TV and couch was valuable so that even though they were 95% used alone, they could be shared with guests.
If I was into media enough to spend $3,500 to have a great experience, it would be a bummer if I couldn't watch a movie with someone else occasionally.
I think a lot use separate apps. I had a gimbal that I used to use with an old iPhone with buttons to move the gimbal and direct the phone, but also with buttons to start/stop recording, and do other things without touching the phone itself. This gimbal was in the $300-$500 range.
8 years of professional experience, working primarially in full-stack web development. I work daily in Python, FastAPI, Ruby, Rails, Sinatra, MySQL, PostgreSQL, Linux, MacOS, Docker, AWS (EC2, RDS, Elastic Beanstalk, IAM), Git. I'm familiar (Use most months) with ElasticSearch, CloudSearch, Tailwind, Vue. As Hobbies, or smaller projects (used on at least one completed project over the past five years): Go, Zig, C, C++, Rust, Phoenix, NoSQL, MongoDB, (probably more, but these were the ones that came to mind.)
I work well with teams but thrive on independent work, and delivering consistent results. As a bit of a heads up, I'm fairly selective about freelance work at the moment.
My day job has me performing two main functions:
- Building full stack web development systems. I generally lean more towards writing backend code, and documenting our infrastructure. UI is my weakest area. This role has me working in datasets with ~1 billion row tables, and search indexes with ~100 million documents. Since we're a small company (~8 developers), I have been a major part of the architecture of our systems over the past 8 years. We've got five separate core businesses that our dev team supports, and I've been a part of architecting and implementing all of them. I would prefer to focus more on backend development in a future role.
- Creating one-off scripts or processes to assist in business functions. These tend to involve quickly reverse engineering undocumented web APIs we have permission to use, and querying them for our customers. At their simplest, these are a mix of writing some SQL and a few HTTP requests. At their most complicated, they have involved designing and implementing a tree structure to accurately model the business domain, and then pulling data about these structures from relevant public APIs.
- This month, I reduced the cost of a company's AWS CloudSearch spend by 80% (over 10k/month) by reviewing their codebase, doing some reasearch, and improving what they were storing and how they were doing so. This required a one-line code change on the existing codebase, and writing a new, short (~500 line) indexer. Doing a deep dive into the single highest AWS line item was the impetus for the project, and frankly, it turned out far better than expected.
Outside of work, I run https://www.thiswebsitewillselfdestruct.com, a website I built and maintain. It really will self-destruct, and it reaches ~100k users and handles ~13M requests each month. Building tools and infrastructure to manage its moderation and keep it a positive community has been a huge learning experience.
- Familiar (Use most months): ElasticSearch, CloudSearch, Tailwind, Vue
- Hobbies (Used on at least one completed project over the past five years): Go, Zig, C, C++, Rust, Phoenix, NoSQL, MongoDB, (probably more, but these were the ones that came to mind.)
My day job has me performing two main functions:
- Building full stack web development systems. I generally lean more towards writing backend code, and documenting our infrastructure. UI is my weakest area. This role has me working in datasets with ~1 billion row tables, and search indexes with ~100 million documents. Since we're a small company (~8 developers), I have been a major part of the architecture of our systems over the past 8 years. We've got five separate core businesses that our dev team supports, and I've been a part of architecting and implementing all of them. I would prefer to focus more on backend development in a future role.
- Creating one-off scripts or processes to assist in business functions. These tend to involve quickly reverse engineering undocumented web APIs we have permission to use, and querying them for our customers. At their simplest, these are a mix of writing some SQL and a few HTTP requests. At their most complicated, they have involved designing and implementing a tree structure to accurately model the business domain, and then pulling data about these structures from relevant public APIs.
- This month, I reduced the cost of a company's AWS CloudSearch spend by 80% (over 10k/month) by reviewing their codebase, doing some reasearch, and improving what they were storing and how they were doing so. This required a one-line code change on the existing codebase, and writing a new, short (~500 line) indexer. Doing a deep dive into the single highest AWS line item was the impetus for the project, and frankly, it turned out far better than expected.
Outside of work, I run https://www.thiswebsitewillselfdestruct.com, a website I built and maintain. It really will self-destruct, and it reaches ~100k users and handles ~13M requests each month. Building tools and infrastructure to manage its moderation and keep it a positive community has been a huge learning experience.
I don’t know the specifics, but a company I worked at definitely decided to get ‘serious about ads’ by hiring a director of marketing and seemingly giving him an unchecked budget.
About 2 years later, he left the company. Very few - if any - customers were generated, but there was a sizable Google Ads spend.
I think the business owners had quite good luck with hiring talented people and letting them get to work, fairly hands-off. The guy spoke well and could quote many marketing gurus. I never found what he said to be particularly useful for the company, but I assumed he was getting results since someone was keeping him around.
I believe many owners of successful businesses have blind spots and need people they can turn to fill them. Sometimes that goes poorly.
Right now I’m fixing a similar snafu where I’m halving a not-insignificant AWS monthly bill for a company due to an ‘expert’ doing something very expensive. Like, 2 weeks of work will cut many developers annual salaries worth of AWS spend a year. Sometimes you get bad advice and you’re growing & making enough money that you can ignore the seemingly huge inefficiencies.
> This makes as much sense as saying that a company spent $1.5 MM on five engineers for a year without a single line of code ever being written.
I mean, if you change this to ‘functional line of code’ or ‘usable line of code’ I have definitely seen that occur with one or two developers over my career.
I don’t think it’s the norm, but I do think it happens.
Yup, He's also a person who's spent an hour talking (on Cortex) about how much he and CGPGrey enjoyed using the Meta Quest Pro for having work meetings together virtually. So he understands the comparisons fairly well.
His review probably made me more excited than anything else to give it a try.
I’m happy to believe that the therapy was ineffective, but I don’t necessarily understand why going off topic is bad. In my experience, I had a lot of conversations with therapists that were ‘off topic.’
I’ve definitely talked poetry and writing with a therapist, and while I’ve never had my therapist provide code, we’ve definitely talked tech in great detail.
Maybe those therapists were intentionally making me comfortable by engaging with shared interests. And the LLM isn’t being intentional about it, but I’m not convinced that a therapist is ineffective if they fail to stay ‘on topic’ when directed off topic by their patient.
It is very much supported. Top left, click on your name, 'Add account', and go from there. I think in the backend the accounts might be associated for security/abuse purposes, but Instagram actively wants you to be able to have more than one account.
I'd imagine it would be a lot harder to avoid being 'thirsty on main' without these features.
Just checked, and signed up with a random second account. They add the phone number from the previous account you were on by default, and mention copying your other non-public information over from the previous account you were signed in to.
I think the easiest solution is to create a second Instagram account. That’s what I did. Instagram supports having multiple accounts signed into the app at once, so it’s not much of a pain once you’ve set it up.
I had an issue where I opened threads before realizing I wanted to create a new Instagram account for it. I had to hard quit the threads app, create the new account on Instagram, sign in with it, then re-launch threads.
> I won't say they are worse at coding, but more that I am more familiar with how dependencies work because I've already done the same thing when I was a junior. Also, knowing who to ask for help also helps a lot.
I might phrase this a bit differently, but I think it’s getting at my thoughts as well.
I work with developers who would destroy me in a race to implement various search algorithms, or whatever discrete metric of coding prowess you want.
What they struggle with is:
- Efficiently getting other teams to answer their blocking questions in a way that makes the other team happy to work with them.
- Understanding the existing features of our fairly complex stack.
- Judging when to ask for help, and who to go to about a particular problem.
- Identifying dead ends quickly, and pivoting to alternative solutions at the first sign of trouble.
- Incorrect assumptions about the company’s priorities, and how the priorities can help shape the request.
I end up in a lot of meetings, but I also occasionally (a couple times a year on average,) take a few weeks and implement a business goal that a team has been stuck at for months/years.
I had this exact same experience. I was happy to move to something good, but I couldn’t find a lot of benefit. Maybe I’m missing something, but the added complexity is not worth it to me for what it provides.
Remote: Preferred
Willing to Locate: No
Technologies: 10 years of professional experience, working primarily in full-stack web development. I work daily in Python, FastAPI, Ruby, Rails, Sinatra, MySQL, PostgreSQL, Linux, MacOS, Docker, AWS (EC2, RDS, Elastic Beanstalk, IAM), Git. I'm familiar (Use most months) with ElasticSearch, CloudSearch, Tailwind, Vue. As Hobbies, or smaller projects (used on at least one completed project over the past five years): Go, Zig, C, C++, Rust, Phoenix, NoSQL, MongoDB, (probably more, but these were the ones that came to mind.)
My day job has me performing two main functions:
- Building full stack web development systems. I generally lean more towards writing backend code, and documenting our infrastructure. UI is my weakest area. This role has me working in datasets with ~1 billion row tables, and search indexes with ~100 million documents. Since we're a small company (~8 developers), I have been a major part of the architecture of our systems over the past 8 years. We've got five separate core businesses that our dev team supports, and I've been a part of architecting and implementing all of them. I would prefer to focus more on backend development in a future role.
- Creating one-off scripts or processes to assist in business functions. These tend to involve quickly reverse engineering undocumented web APIs we have permission to use, and querying them for our customers. At their simplest, these are a mix of writing some SQL and a few HTTP requests. At their most complicated, they have involved designing and implementing a tree structure to accurately model the business domain, and then pulling data about these structures from relevant public APIs.
- Miscellaneous tasks as they come up, recently, I reduced the cost of a company's AWS CloudSearch spend by 80% (over 10k/month) by reviewing their codebase, doing some research, and improving what they were storing and how they were doing so. This required a one-line code change on the existing codebase, and writing a new, short (~500 line) indexer. Doing a deep dive into the single highest AWS line item was the impetus for the project, and frankly, it turned out far better than expected. Outside of work, I ran https://www.thiswebsitewillselfdestruct.com, a website I built and maintain. It really will self-destruct, and it reaches ~100k users and handles ~13M requests each month. Building tools and infrastructure to manage its moderation and keep it a positive community has been a huge learning experience.
Email: [email protected]
Good luck with whatever you're working on!