superdug

Hello internet friend,

As others have mentioned, you are arguably not as close to rock bottom as one can be. I hit rock bottom when I lost my home, my job, my ability to walk, was on assistance and bought my groceries with food stamps. How I got to rock bottom is a story for a meeting.

I found solace in recovery. Recovery is different for everyone as is rock bottom. Therefore if you feel you've lost more than you were willing to and you're at a precipice of a major life change that will bring you up out from the bottom, or you'll find rock bottom can even be lower than your realize. Again, what that means is going to be different for everyone, but if you have a need that you must change something in order to be better, then you already know what to do. Obviously if you're addicted to heroin, that change would be sobriety and recovery.

I'm not trying to give you answers as those are things you're going to have to figure out for yourself.

You've been around for three decades and been adulting for less than one. You've got at least 4 more decades to define yourself and your life. The best part is, you are the director, producer and actor in how that future pans out.

Right, but the implication of your background lends one to question, is the user part of the product?

Google and Youtube are advertisers who monetized search queries and content consumption of their users as the end result of their product.

You've not addressed the core of the argument whereby you admit and extol your previous experience, but neglect to decry the actions the company took while you were there.

You want to have control of the flow of information, but you are not a charity and not opposed to reimagining a product to better monetize it.

I've got a few of the bongos dream dorm posters in storage, last offer was $300 a-piece, I've held on to them and given them as gifts for people impossible to find gifts for.

My first job out of college had layoffs 8 months in. I was called into a conference room, connected to a speakerphone with the rest of my team, immediately told that we were all laid off and that I had some paperwork to sign in my managers office.

I was given a 33% raise, moved to a salaried position, and got a $5000 cash bonus 10 minutes later.

I had mastered the new system we were implementing and converted and supported the remainder of the customers from the legacy system. Shitty support of the product my team of now one actually drove revenue as the customers would pay higher support prices because of the shitty support I offered.

The service I offered was shitty because my job was to meet minimal contractual obligations for multi-decade contracts to persuade the customers to renegotiate the contracts for a product that hadn't been EOL'd. All the while offering onsite conversion services from the legacy product for most of my day job.

What I'm saying is that company is still alive today, they had a pivot point and literally cut 55% of their employees on a single day.

Google wants to beat facebook still, there is one of a billionity pivot points that twitter could take.

I will just wait for the bug the breaks the camels back here.

There will be a necessary breaking change that there will be no support for that will cascade into the downtime the media is demanding at the moment.

So don't?

At the very least write an explicit unit test for whatever it is. If someone breaks it, at least it will be on your landmine and not at deploy or worse. If you setup a potential for improvement, protect the functionality and ensure it is successfully the next persons problem, but can situationally identified in the future.

There are a lot of approaches to this. The way I'd approach something like this, is to find something fairly trivial and just do it. Then ask what you should do with it. I've always found starting a conversation about untracked, but completed useful, change and how to get it done "the right way".

See where the conversation goes from there.

I decided to wade through the comments to see if this article was in fact as not-news to me as it was to someone else.

I'm not trying to be drab on the article, nor people who found it to be something new that they just learned.

I will echo your sentiment and add that lead is also listed legally as a "hazardous substance" here in the US which means that incentivizing it to be recycled is the most economical while also being ecological.

full stop ... if you want my commit to be perfect ... make a unit test I can run on my PR.

Meet my need first, and I will automatically meet yours.

Oh my, that comment was made in jest I swear, it was the very few things lacking in the site. The counter was there, the animated gif, center tags, etc. I just noticed two things that stuck out as missing to me.

It's a red flag to assume that I'm going to want a raise, regularly? I don't know that it's my undervaluing of the work that's the problem ... I'm fairly certain that the company undervaluing my work is the problem that makes me leave.

no embedded sound and no blink tag ...

I've always been told that short tenure is "red flag" and I think it's bullshit.

I've accelerated my net worth by a rate of return of 12% compounded over the last 20 years of professional life. My resume has 10 separate entries in it which means I last on average two years.

Why do I expire after two years? Because no one in my industry gets promoted from within. No one in my industry is ever given more than a cost of living wage increase, and certainly not a 12% year over year average increase. It takes two years of watching people get hired over you with no raise to decide that you deserve more money and you go out and find it.

I believe in judging my value in monetary terms and as I increase my experience, knowledge, and value, I expect that amount to increase as well.

It looks like something interesting, I sent an email as I got stuck after the read me and haven't had a lot of time to poke around in the code.

Thank you! It was bothering me as well. I speak very little Japanese and was honestly curious. Maybe that was part of the point?

I'm honestly curious. Can you elaborate?

Why don't you just illuminate the room 24x7 with green overhead lights? And by green, I mean the color itself. I've found that you can operate in the room and with the complete absence of both red and blue all photosynthesis should be halted.

If you use a static site generator and it's in gitops, you can drop all of the considerations of AWS and focus on one control panel inside of Cloudflare and the content of your page. That's the benefit.

I've noticed that Cloudflare documentation is lacking, but I rarely find information that is published on official sources that is out of date. I find the fact that there are two dozen sources of information out there for an AWS or Terraform configuration, but they're all still wrong because the API has since changed and the documentation wasn't cleaned up when the breaking change was made.

I have found that with Cloudflare's documentation that where it's lacking they have the ability to PR in changes and if you go back to a saved page, I've found them pleasantly updated numerous times.

Thankfully the cutting edge development is based off of open standards that you can easily build off of. I know personally that I've found most of the sticking points of developing against Cloudflare to be easily mitigated and just be an overall better experience as a customer than with another hosting provider.

It doesn't hurt that they aren't charging me all that much personally, but I have a day job that fills up the Cloudflare stock price just fine.

I'm curious about cams, but I'm being greeted with "Your passphrase has expired" when I try to get it to "let me in"

This page inspired me to actually convert as well. I have just recently been forced out of the AWS free tier and for some reason my insistence on using terraform and preserving a dynamic lockable state was somehow costing me $20 a month in DynamoDB costs.

Anyways, the pages import to take an existing git repository with a slew of CMS systems (mine being Hugo) supported, and the ability to just publish it to a custom domain in a series of clicks was actually really simple.

I think I dedicated 30 minutes of entire work and just saved ~$20/month because of it.

vscode in github, simply replace any github.com url with github.dev and you've got a full vscode environment with github plugins right in the browser.

What does this mean for miniflare?

Currently there is no way to test for cloudflare-esque failures. For instance, what does my worker do when the kv lookup fails or another cloudflare infrastructure related promise isn't fulfilled? I think actually running the true worker runtime in a testing environment is key.

absolutely key point here. miniflare doesn't allow you to check for conditions in which cloudflare might not fulfill a promise, but can't actually be tested for as the infrastructure is simply represented as an artifact currently with miniflare

This is great, and I think if it was fully adopted initially in greenfield, this would be a completely feasible solution. My question is though, these problems exist at large organizations and will be seen as "another tool to rule them all" synonymous with things like "sharepoint". Disclaimer: I'm not saying that backstage is anyway comparable to sharepoint except that it presents itself as this grandiose solution to all things on boarding and learning on your own.

With that said, what's the low hanging fruit to entice adoption of backstage into an organization that already has a "process" like mentioned in the article of whiteboard meetings with stakeholders. Obviously that's not a great use of time, but it's also no extra learning or work, that SME can talk about their function without any preparation and can interactively answer any questions the learner asks at the time.

That doesn't scale in practice, but it also doesn't require any more whole team buy in

It's just a wallet with a bubble on the outside shell that holds the air-tag in it ... doesn't stick out too far and fits fine in my pocket

Am I a realist on Apple Apologist?

My primary credit card is an apple card, primary dev machine is a mbp, primary work machine iPad, phone iPhone, watch Apple, and I have air tags attached to my dogs and wallet.

In this ecosystem, I can reference _ANY_ of my screens for necessary and current relevant information whether it be curated or automated without breaking a glance to whatever primary device the content came from.

I can air drop to my screens and other people in my family whenever I want to share anything from any of my devices.

It's a walled garden sure, but the toys in here are fantastic.

I also have Apple One service because of the iCloud storage alone between devices and Apple Music/News is actually a nice service.

So I guess I understand the "Oh no big company taking over more of my stuff that I think I should diversify because it seems like the right thing to do", but I guess I'm just too used to things just functioning well that I get over how "limited" I am.

You should probably avoid any phone that isn't an iphone then...

Looks to be 113 of them in stock right now

I've switched to using an iPad pro for all of my productivity and media consumption needs. With stage manager and an external monitor, it's going to become a very capable workstation, as it already is for me.