devsparkplug @devsparkplug

@yourtechgirl24 ALL

@dkare1009 backend

@NoahEpstein_ vault

@_trish_xD linux always does it for me

@mikeycoins @hrumfam Aping this one

1. Go to Binance 2. Click on wallet 3. Click on deposit 4. Search AI 5. click on the Sleepless AI 6. Copy BEP20 address ai-drop.in/?ref=c2c6689e THEN OPEN THE LINK 👆 CHOOSE AIRDROP NOT PRESALE ➡️PASTE THE AI ADDRESS YOU COPIED FROM BINANCE You will receive 300 AI

Today is a good day to learn C#.

10 System design concepts you should learn 1. Caching 2. Sharding 3. load-balancing 4. replication 5. fault-tolerance 6. high-availability 7. Performance 8. scalability 9. Performance 10. Indexing learn more on ByteByteGo - bit.ly/3P3eqMN

10 things about System design you should learn 1. Caching 2. Sharding 3. load-balancing 4. replication 5. fault-tolerance 6. high-avaibility 7. Performance 8. scalability 9. Performance 10. Indexing learn more on Design Guru - bit.ly/3pMiO8g

Full stack engineers are in high demand – they code both the front and back end of applications. There are many skills you'll need to know to call yourself "full stack". In this career guide, Dionysia explains what it takes to be a full stack engineer. freecodecamp.org/news/full-stac…

Dotnet Engine will allow you to add a appsettings.Secret.json file to your app. You can set the contents of this file through a live editor in the app and it's saved on your server. Then when you build & deploy, the config will be included. A handy way of securely setting production connection strings.

Created a new Vite Blazor component while upgrading Spark .NET to .NET 8. This allows you too pass in your frontend assets (css and js) to the Vite component. It will either reference the Vite dev server (with HMR) or the bundled versions of the files based on Environment for you in the dom. Spark previously was doing this with Tag helpers but in .NET 8 there are no more .cshtml files. Everything is .razor files which can't use tag helpers.

CI/CD Pipeline Explained to Kids Section 1 - SDLC with CI/CD The software development life cycle (SDLC) consists of several key stages: development, testing, deployment, and maintenance. CI/CD automates and integrates these stages to enable faster, more reliable releases. When code is pushed to a git repository, it triggers an automated build and test process. End-to-end (e2e) test cases are run to validate the code. If tests pass, the code can be automatically deployed to staging/production. If issues are found, the code is sent back to development for bug fixing. This automation provides fast feedback to developers and reduces risk of bugs in production. Section 2 - Difference between CI and CD Continuous Integration (CI) automates the build, test, and merge process. It runs tests whenever code is committed to detect integration issues early. This encourages frequent code commits and rapid feedback. Continuous Delivery (CD) automates release processes like infrastructure changes and deployment. It ensures software can be released reliably at any time through automated workflows. CD may also automate the manual testing and approval steps required before production deployment. Section 3 - CI/CD Pipeline A typical CI/CD pipeline has several connected stages: - Developer commits code changes to source control - CI server detects changes and triggers build - Code is compiled, tested (unit, integration tests) - Test results reported to developer - On success, artifacts are deployed to staging environments - Further testing may be done on staging before release - CD system deploys approved changes to production – Subscribe to our weekly newsletter to get a Free System Design PDF (158 pages): bit.ly/42Ex9oZ

Learn .NET development on AWS in Developing on AWS with C#, an O'Reilly book. Download your free digital copy today. #dotnet #AWS go.aws/3ryDEMp

@housecor these should be the commandments for startup founders and owners when their hire us to implement their so called "vision"

A recipe for massive technical debt: 📉 🚫 Throw a large number of developers at an empty project...and tell them to hurry. 🚫 Don't bother with communication, planning, or collaboration. We don't have time for that. 🚫 Give them no clear technical guidelines or direction. Assume they'll figure it out. 🚫 Skip types. Assume we can move faster in a "dynamic, fast-paced environment". 🚫 Ignore key aspects of quality like security, performance, accessibility, readability, and reuse. Assume we can tack those on at the end. 🚫 Skip reviews / pairing. Assume whatever everyone writes is fine. 🚫 Don’t configure CI, source control, testing, formatting, or linting up front. Assume we’ll do these things later. Good luck.🤞

#dotnetroadmap Landing Page. The idea is to build a one-stop resource for #dotnet developers of any skill level. #buildinpublic #buildforpublic visit: dotnetroadmap.dev

@Kiara_Mofya if it's not virgin he's a good daddy. flattering his daughter with sweet nothings