Rudi Garcia heeft de vibes van zo een getroubleerde detective in een Zweedse politieserie die de hele reeks lang met iedereen ruzie maakt maar dan wel de moord oplost.
STOP USING YOUR NOTES APP AS A PASSWORD VAULT
STOP USING YOUR NOTES APP AS A PASSWORD VAULT
STOP USING YOUR NOTES APP AS A PASSWORD VAULT
STOP USING YOUR NOTES APP AS A PASSWORD VAULT
STOP USING YOUR NOTES APP AS A PASSWORD VAULT
STOP USING YOUR NOTES APP AS A PASSWORD VAULT
big news: @intigriti is now integrated into https://t.co/725Q02zI9r!
Not only that, but they're integrated through an API key instead of .eml file, because the @intigriti dev team actually made a special endpoint for us! In 3 DAYS! During the end-of-year holiday season!
🪨⭐️!
@ThePrimeagen The most amazing achievement of the computer software industry is its continuing cancellation of the steady and staggering gains made by the computer hardware industry.
- Henry Petroski
Do this:
1. Open AWS and create an account.
2. Go to EC2, spin up an instance, generate a key pair, and SSH into it from your local system. Just play around install Nginx, deploy a Node app, break things, fix them.
3. Decide to launch something? Go to Security Groups open ports for HTTP (80), HTTPS (443), and SSH (22).
4. Grab your instance’s public IP, open it in your browser, and you’ll see your app running on the cloud.
5. Start scaling ? create another EC2 instance and set up an Application Load Balancer to route traffic.
6. Tired of adding instances manually? Use Auto Scaling Groups (ASG) define min/max instances, attach a launch template/AMI of your app, and AWS will scale automatically based on CPU or request load.
7. Getting millions of requests and your DB is choking? Use Kafka or SQS for buffering high-throughput workloads. Learn more about async
8. Store images, videos, or backups? Use S3 connect it from your app via the SDK, and make a file uploader.
9. Use RDS for managed databases (MySQL/Postgres). AWS handles backups, scaling, and maintenance.
10 Use CloudWatch to monitor your instances, logs, and metrics. Set up alerts when CPU spikes or memory usage is high.
11. For networking, explore VPCs subnets, route tables, gateways. This is where you learn how AWS isolates traffic securely. You will learn really well about networking here. Just create a vpc and play around
12. Once you’re comfortable, try Terraform to automate infra because that's 100X easier to manage state.
Stage 13: Say Fuck AWS for stealing money and buy your own VPS, set up Docker, or use Coolify for one-click PaaS setups.
Imagine working at Pornhub. At like the corporate office as a developer or whatever. White collar. That’s gotta be a weird job. Working there has gotta be fucking weird.
Open source once ≠ open source forever
#dotnet
Specific versions of open-source projects remain licensed under the terms they were released with forever. But that doesn’t mean future versions must also remain open source.
If a NuGet package was OSS at one point, the author is under no obligation to keep it that way. They are well within their rights to change direction, and in many cases, that shift is necessary for long-term sustainability and ongoing maintenance.
The comment below was left on a post I shared about the newly announced MediatR commercial pricing. It’s a fairly common take I see around OSS:
"I have no problem with people getting paid for the value they create... BUT..."
The risks of depending on OSS are well known. If a project changes direction, it’s not a “shitty move” or a “rugpull.” That kind of reaction misunderstands the voluntary nature of open source and wrongly assumes the author owes us free work forever.
Have you got thoughts here? Please comment below.
in 30 years i’ll probably be up to some boomer stuff, like ”NO SON OF MINE IS MARRYING AN LLM, MARRIAGE IS BETWEEN TWO HUMANS ONLY”, and my kids will be like ”OMG dad you’re so robophobic!!!”