The center section of my last sectional broke after about four months. Should any section break, I can quickly replace that piece instead of having to "deal with it" or replace the whole thing.
147 karma · joined March 17, 2011
The center section of my last sectional broke after about four months. Should any section break, I can quickly replace that piece instead of having to "deal with it" or replace the whole thing.
Once you get the config and include syntax for Jekyll, it's a piece of cake.
I really like being able to add One-Time Passwords to any record, so we're not dealing with additional auth apps. The browser based UI makes it easy to add or update logins as you go. In addition, having controls to recover an account for someone that's locked out and has lost their Emergency Recovery Kit gives the execs some peace of mind. The secret key changes, so the old ERK is invalid should it be found later.
Individual and team level controls are available. We have some shared accounts, but you can create as many Groups and Vaults as you need. You can set access rights at multiple levels. So one group/person may be able to edit records, but another group/person can only read them to log in.
https://support.1password.com/create-share-vaults-teams/
Brian already mentioned the free family account. It's brilliant.
https://palant.info/2023/01/23/bitwarden-design-flaw-server-...
https://www.cockroachlabs.com/blog/what-can-we-learn-from-ou...
"Years ago I dedicated a Flex Friday (our version of 20% time) to stargazers, a tool to query the CockroachDB repository for information about its GitHub stars and analyze the results. At the time of writing, we had 6,000+ stars (which felt like a lot), and the data in this blog will be based on that original set of 6,000 stargazers."
Which links to
https://github.com/spencerkimball/stargazers
"GitHub allows visitors to star a repo to bookmark it for later perusal. Stars represent a casual interest in a repo, and when enough of them accumulate, it's natural to wonder what's driving interest. Stargazers attempts to get a handle on who these users are by finding out what else they've starred, which other repositories they've contributed to, and who's following them on GitHub."
EDIT: Found it! https://youtu.be/1SNxaJlicEU (slightly NSFW, skip to about 3:30)
Desktop PC - General browsing and light gaming.
Laptop PC - Work
15" Macbook Pro (Intel) - Work (deprecated)
16" Macbook Pro (M1 Max) - Work
iPhone 13 Pro Max
iPad Pro M1
Amazon Fire tablet for guest access to wireless audio.
Monitors 3 x 27" Acer IPS 2k monitors
3 x 27" LG IPS 4k monitors
Protip: A 27" 4k monitors is a waste of a 4k monitor. Text is waaaay too small for coding at that resolution.Everything else has been sold or recycled. I used to have PILES of desktops and servers, but I got over my nostalgia years ago.
Except for Steam AND Battle.net (Blizzard) which both have their own dedicated 2FA apps.
I use 1password to manage all of this and the only thing compliant is about some sites that seem to break a password manager's ability to auto-populate form fields.
At a previous employer, the solution was to move off SMS and onto internal messaging via native mobile apps. This will shift your cost focus, but that levels out as the volume of SMS transactions decrease.
Famous last words. I once found an egregious security violation at a previous employer. Was told it was a "temporary fix" that's been going on 7 years.
You might look into putting all of the static files into source control, but ignore the folders full of uploaded documents (the videos, etc.). Then you can at least track changes and deploy updated HTML via a managed process. You should back up the large files and figure out how you're going to serve those.
Jira will translate the old ticket URLs to the new ones. I did this earlier in the year to effectively sunset an overloaded and unfocused project and transfer only the tickets we would continue to develop. The old project is essentially an archive and the new one has more focus on what the team needs to deliver. I also created additional projects for tickets that need input from the business users so they can agree on what they want before dev is even aware of them.
This is exactly the situation with a number of long-standing, formerly popular languages. ColdFusion and PHP jump to mind. They're fine languages and people love them, but if no one's paying, why bother sticking to them? Loving a programming language doesn't pay the bills.
"I'm sure it will keep providing as long as Ruby engineers become founders or companies keep maintaining legacy projects built with the technology."
My previous employer was maintaining over 30 acquired company's worth of legacy code bases. They replaced common functionality via new microservices and would sometimes replace an entire product via a new acquisition. It's sometimes a better ROI to replace instead of maintaining or building.
https://twitter.com/threadreaderapp?lang=en
From any tweet in the thread, mention us with a keyword "unroll"
@threadreaderapp unroll
And it converts the entire thread into a blog post on their site.