For bonus points, the participants of the b) and c) options should be forced to pay back whoever funded their research.
12,970 karma · joined January 7, 2009
Formerly: Twilio, Okta, ngrok, Pangea Cyber, and lived in DC & Austin
My contact: keith @ (my username).com
[ my public key: https://keybase.io/caseysoftware; my proof: https://keybase.io/caseysoftware/sigs/MoF3-kI9MgdujWA933IcxPdYy7T-qs2bViw5BdQoepI ]
For bonus points, the participants of the b) and c) options should be forced to pay back whoever funded their research.
If think you're really close with one nuance.
Business does not value CODE quality. Their primary goal is to ship product quickly enough that they can close customers. If you're in a fast moving or competitive space, quality matters more because you need to ship differentiating features. If the space is slow moving, not prone to migration, etc, then the shipping schedule can be slower and quality is less important.
That said, customers care about "quality" but they likely define it very differently.. primarily as "usability"
They don't care about the code behind the scenes, what framework you used, etc as long as the software a) does what they want and b) does it "quick enough" in their opinion.
In Texas, residential grid-tied solar can be up to 20kWh so I chose cells that got me to 19.96kWh
Then I added an 29kWh battery stacks (18kWh total) but each stack could go to 18kWh (36kWh total). Then I also used a pair of Generac inverters which lets me get two more stacks for 72kWh total.
My goal was resiliency, not sufficiency, so I use it grid-tied so I charge during the day and use at night. When there are storms coming, I flip it to "priority backup" which will prioritize charging.. even using the grid to do it if there's not enough sun.
Anyway, it's been in production since January '22 and my annual* electric bill is ~$1100. Even better, when we have an outage (occasional as we live in a heavily wooded area) if our stack is full, we have ~5 days of battery backup for the fridge, a handful of appliances, and our Starlink.. therefore we have safe food storage, safe food prep, and non-terrestrial communications.
Of course, this cost ~$80k to get there in 2021 (aka before crazy inflation)
I recently created an course for LinkedIn Learning using generative AI for creating SDKs[0]. When I was onsite with them to record it, I found my Github Copilot calls kept failing.. with a network error. Wha?
Turns out that LinkedIn doesn't allow people onsite to to Copilot so I had to put my Mifi in the window and connect to that to do my work. It's wild.
Btw, I love working with LinkedIn and have 15+ courses with them in the last decade. This is the only issue I've ever had.. but it was the least expected one.
0: https://www.linkedin.com/learning/build-with-ai-building-bet...
They don't even pass a budget anymore.. which they're explicitly required to do. They learned there are political consequences to their action so they handed their job to agencies in the Executive Branch to write their own rules which acted like laws.
When SCOTUS struck down Chevron Doctrine last year, it boiled down to "No, Congress writes the laws."
The fix is Congress doing their job.
Did the pay full retail price for the product or get a discount?
Did they get the product at release or in advance?
Did they get access to detailed specs or the people who built it?
Did they give feedback that went into the product?
Did they get a company/lab/event visit and some swag?
Did they get preferential access for the next product?
"Sponsoring" is just the most visible, clearly disclosed way to advertise in those. But fundamentally, getting and preserving access is immensely valuable and there may not be funds moving between the two groups.
None of us are completely unbiased. Getting those things disclosed would be a great improvement.
If you know of a webhook provider not in my list - https://webhooks.fyi/docs/webhook-directory - let me know and I'll make sure it's added.
In the US, I've worked with the team at https://www.optimalcounsel.com/ before. They're great and founder-focused so generally get it and are reasonable on pricing.
Before you talk to an attorney, make sure you have your agreements together. That is likley your initial employment agreement, any grant docs, your separation docs, and the current agreement they want you to sign.
And yes, don't wait. If you need to take action, you may need to have time to ship docs, send wire transfers, etc.
Technically true but just a lawyer's time (for "free") is significant. Throw in other prosecutors, investigators, etc and it begins to look "limitless". And beyond that, with a gun charge, it could be escalated to the state level pretty quickly. Alternatively, if he illegally possessed it - common if there are drugs - it could qualify for Federal charges.
It's up to the prosecutor(s) to decide what the charges are and at what level, therefore they get to decide what resources to expend.
The State has near-limitless resources, therefore they MUST be held to the highest of standards.
I'd even be in favor of censuring/firing the investigator involved who left information out of the warrant. Future defense attorneys will be able to bring this up on every affidavit or testimony he gives and some portion of cases will fall apart as a result of this.
"Do it the way we want or die" is a pretty bold take.
Are you going to enforce this or demand to have law enforcement or even military units do it?
When the stakes are exceptionally high, don't ask for advice from someone paid by the agressor.
You need a trusted advisor on your side who can look at it with a calm mind and perspective on what is normal, acceptable, and legal. You're young and have been slapped around, seemingly inappropriately.
If you were in physical pain, you'd talk to a doctor to assess and get recommendations before treatment. Do the same here.
Anyway, here's some talk of the business model and mis-matched motivations:
This depends on at least four premises:
a) that your wages at least track with inflation
b) that your expenses (not debt) track less than inflation
c) that you can buy into stocks/bonds before the inflation AND they track at least with inflation
If any of those are untrue, your conclusion falls apart.
If all three are untrue, your expenses are growing faster than your wages and the little you have left over is now buying already-inflated assets.. which we've seen play out once in recent times.
Short term thinking in itself is damaging.
But then thinking something is "worth more" because it costs more dollars a year from now is deceptive.. how much did its value increase vs the dollar decrease?
But it's convenient for tax authorities as you're taxed on the gains, regardless of the why/how it changed.
Moving such a document is extremely risky and a lot of work so not worth it in almost any case short of the PR bump/curiousity of having the "world's oldest bond"
In 2021, it was 22p/kWh and in 2022, it went to 44p/kWh.
It's come down 6-7p each year since but doubling in one year is crazy.
The other challenge was customers who wanted groups to show up in a particular order. Since it's was literally just an array (no keys), it was just a giant alphabetized list.
Then the problem came when people used group count limits. Your group "AppDev" was always fine but "TestGroup7" may not be.. depending on how many groups the user was in and/or how they filtered those groups.
Figuring out that one out was terrible.
https://developer.okta.com/docs/concepts/api-access-manageme...
Section 5.1 of the OIDC spec says the standard claims can be in the ID token and/or at the Userinfo endpoint. Further, Section 2 says "ID Tokens MAY contain other Claims."
Unfortunately, one of the most common use cases for the ID token was to add someone's Groups, usually from AD. We had a number of customers with users who had a LOT of groups. I remember one where their users were in an average of 700 groups and one user had ~9000. These groups could be anything from the AD group created yesterday for a new app to that group from 15 years ago that no one wanted to delete just in case. This made for gigantic tokens.
Anyway, to address this scenario, someone at Okta came up with concept of the "fat ID token" and the "thin ID token". The "thin" would always come back with the access token on the inital request and the "fat" would only be available via the userinfo endpoint where we weren't limited by payload sizes.
So yeah, now you know and sorry about that.
This doesn't bode well for open source software not backed by a "company" that can write these roadmaps and deliver on them.
aka Sounds like Microsoft, Oracle, and other's lobbying has been effective.
Don't risk it, just use their machine.
There are so much better, more important and meaningful things to fight.
If you have an LP or wire spool recording, the audio is the key, obvious work. But then you have the album cover, the spool case, and the physical condition of the media. Being able to see an album cover or read a reporter's notes/labeling is almost as important as the audio.