I attempted to handle some of what you're suggesting via the plugin ecosystem utilizing a vector database for RAG, and LLMs to auto-suggest tags or related docs. None of the plugins seem to get this quite right. The extensions were pretty brittle, and limited in terms of what they could do with the open doc. I now do most of my new note creation/editing and organization through cursor and custom built agent flows. The obsidian app is now just for mobile access and sync.
Cursor is better suited for enterprise. You get centralized stats and configuration management. Managers are pushed for AI uptake, productivity and quality metrics. Cursor provides them.
Doesn’t hurt. Be prepared for resistance though. The steroid taboo means there are very few doctors in the US that are both experienced and comfortable prescribing.
I saw massive results at 1ml per month, try pitching that. The dose is so low it rules out abuse and lowers the possibility of side effects.
Agree. Also testosterone. I was lucky enough to have lab work before and after getting covid twice. My T numbers halved in less than a year. I was still within the “normal range” so it took some arguing with the doctors to get a prescription for a very low dose. Within 24 hours of starting, I felt like myself again. Brain fog was gone, energy was back, my mood rebounded. No negative side effects thus far. I had tried a lot prior to starting: intense therapy, ketamine, lots of exercise, losing weight, supplementation, lots of lab work. Nothing was as impactful as getting that jab.
Side note: the normal range for T is so wide that it’s meaningless.
F1 isn’t even about max performance, it’s about trying to maintain an element of driver skill as a factor of outcomes. It’s why they outlawed the Williams continuously variable transmission (CVT). A lot in F1 is done to maintain the suspense/excitement of a race for the TV audience.
This is sort of highlighted by other comments, but GC is only good at small quick requests. If you're dealing with large or slow requests it results in large or long lived allocations which causes havoc with GC. This is true for any generational GC, Java included.
Also node will only perform well if that IO is offloaded to the kernel or CPP code and behind a future via epoll etc... If it's in the actual node runtime it'll perform poorly because it'll block the thread.
I call B.S.. He's conflating two things. One is a deployment infrastructure, another is an application pattern. I can deploy a monolith in k8s and I can deploy micro-services on a single server or a fleet of on-prem servers using any of the legacy dev-ops deployment automation tools. Sure k8s makes doing micro-services easier because it’s got a lot of the raw building blocks necessary to handle the CD process but in no way are the two concepts related. They’re tackling different problems. He's making the same mistake that he's criticizing others for by equating the two. What he is really describing is an organization doing a “big bang” refactor with poor planning and execution.
I was an engineer at PGP from 2004-2011 and ended up running the server team as lead engineer. I wouldn't disagree with most of the points brought up by the author, both the code base and standard has accreted over time and it's incredibly complex. There were only a couple of people on the team that really understood all the facets of either the OpenPGP or SMIME/x509 standards. It's made worse in that it was a hack on top of another system that had accreted over time (email) and that system was never intended to be secure. We had massive database of malformed or non-compliant emails from every email client since the beginning of time. The sub-packets that the author mentions were primarily used for dealing with forwarded chains of encrypted email messages where each previous message had it's own embedded mime-encoded encrypted/signed messages and attachments.
The problem is that no-one else has gone through the process of establishing a community/standard that's capable of replacing it. Each system has built their own inoperable walled garden that doesn't work with anyone else, and none of them have a user base large enough to make encryption easy and pervasive.
My own secret hope is that Apple is forced to open iMessage as a part of an anti-trust action and that acts as a catalyst for interoperability.
I wouldn't say it's super common. Of the 20-30 founders that I know well I'm the only one I'm aware of that has a nuvigil prescription. I take it because I'm a single parent of young kids and do a lot of international business; my sleep schedule is pretty screwed. I'll use it to combat a sleeping med in the AM and attempt to get back on a normal schedule.
Adderall is pretty common, but they usually take it for ADD or depression. When I see Adderall get "abused" it's usually people using it before going out drinking and not necessarily for work purposes.
Infrastructure automation and AI company, seeking go and infrastructure engineers to work on our deployment, metrics pipelines and NOC infrastructure. You'd be working on some of the largest no-sql deployments in the world (>10s of thousands of servers). Must be able to pass background check.
Configuration comes from the environment. We store the configuration per cluster in a centralized store (C*, etcd, SimpleDB). We bake images that contain everything else.
Depending on the customer and the tech involved we'll do blue-green by doing a controlled rolling push of the config or image after it makes it through the dev/test cycle. Also depending on the type of tech we'll store actual data on network or host volumes.
Individually I charge several orders of magnitude greater than what you're quoting. I'll advise and design, do deep troubleshooting etc.. Consultants that work for me (I'm the CEO) or a large SI will do the implementation.
I do a mix of pure consulting but also managed services. I typically have a 12 hour SLA for issues, and 1 hour SLA for some customers. 24/7 support for mission critical, revenue generating systems. So no, I'm not just a talking head. It's usually me in the NOC on the hook in case things go wrong. I'm the world expert in this field, if you want things to work at scale people call me.
It's a mix. I'm a consultant that specializes in large scale distributed systems. I have some customers that have >100k production database nodes. I manage probably >50PB of data. I have designed large distributed systems for more than 100 customers.
Some systems cope with failure better than others. Everything you've said is also true of DB running on top of a uniform linux stack. From my experience (500+ large scale production deployments) this doesn't happen very often.
Does it solve all problems? No. Does it make the world a little better and is it better than monolithic single points of failure? Yes.