Catfish is delicious

Once you are conceived, you are implicated

@timothy_mukoro 😂😂😂😂

If AI take my job, I'll join this boy and take AI jobs😂

@KelvinRubbie @danielmedupin I miss 2009

@danielmedupin @ronnell66

Life hack: if a project isn’t flowing as it should, pick up a new one Then go back to the previous Works along any facet of life, go do sth different entirely and come back to it

@terrificprodigy 🤣🤣🤣

@CodingIncloud_ 5 months self-study.

How long did y'all study for the CISSP before sitting for the exam?

@KharayKrayKray Mike chapple❌️ Pete zerger❌️ Prabh Nair❌️ Andrew Ramdayal❌️ Jason Dion❌️ Random guy on the Internet ✅️

An attack surface is all the points on a system where attackers can attempt to penetrate or interact with a system. They’re what attracts attackers. The more the attack surface exposure, the fewer skills and attack vectors that are needed to attack the system, and the more attackers you will attract. System designers must aim to limit attack surface exposure as much as possible, as they’re not just another part of the system. They’re crucial and could grant unauthorized access if not properly secured.

@Starman_sdfr @CodeWithKyrian @PhaNhie_01 🤣🤣🤣🤣valid!

@CodeWithKyrian @PhaNhie_01

How do y'all summon the courage to put what you're building out there?

@_collins01 @KelvinRubbie If I were tasked with muted words feature I just know my dumbass won't catch uppercase/lowercase constraints.

@KelvinRubbie Share a piece of lore

@bumi_oye yeah. also started with react and then drifted to vue and have been on it since. I find it more comfortable to use.

I picked up Vue in a few days thanks to my React background and built a fast, searchable image gallery using Vue + the Unsplash API (infinite scroll, masonry grid, teleport, etc). Check the full write-up here: dev.to/bunmioye/i-tho… #vue #react #frontend

@Awakenjp @RecycledTwts

Wrestling is not a sport, Idk why you added John Cena

@mysticwillz Doing the Lord's work.

You're in a backend interview. They ask: "Design a secure password reset flow. What are the key things to get right?" Here's a solid answer 👇

@Limtech001 @thanipro @iamKingRobert @Jasonviipers @jc_coder1 Thank you so much for recording this

Huge thanks to the amazing speakers who broke down Core Backend Architecture in our 4hr Space! @thanipro @iamKingRobert @Jasonviipers @jc_coder1 Grateful 2 everyone who tuned in, asked questions & shared insights 🎧 Recording is up! Part 2 continues on Wednesday; don’t miss it.

@Dghost_Ninja @hackSultan Hi @hackSultan check this out.

Hi @hackSultan . My name is Samuel. A cybersecurity enthusiast specialized in Application Security Engineering and Penetration Testing across Web, API and Mobile applications. I recently built

@KelvinRubbie Thought I was gonna change the paradigms of software and inspire the next gen fr.

Being comfortable with yourself is the ultimate life hack. This world is wired to trip us all. Be honest within yourself, and try not to fit into what is not for you. People respect honesty when they see it.

@KelvinRubbie Bravo brother!

just wrote this reactive table input in dioxus. the whole thing is generic, cells could be anything!

"Going Native - Malicious Native Applications" - by Protexity: protexity.com/post/going-nat… - interesting read about using applications with Subsystem: Native for offense

If you are in tech, and looking for some books to read, then this post is for you. > tcp/ip illustrated > c++ concurrency in action > c++ software design > 100 go mistakes > operating system concepts > designing data intensive applications > operating systems three easy pieces > modern operating systems > code complete > refactoring > effective c++ > the mythical man month > clrs > systems performance > the linux programming interface > computer systems a programmer's perspective > masters of doom > game engine architecture > real time rendering > game programming patterns > game engine black book doom 3 > game engine black book wolfenstein 3d > inside the machine > pragmatic programmer > domain driven design credit/follow: @RubenVeidt

Linux for Beginners - Start here if you’re getting into DevOps 1. Basic Shell Navigation Learn ls, cd, pwd, mkdir, rm, touch. You’ll use them daily in scripts and terminals. 2. File Permissions & Ownership Understand chmod, chown, umask. 3. Package Managers Use apt, yum, or dnf to install tools on Linux servers. 4. System Services Control services with systemctl. Knowing how to start/stop/restart daemons is essential for debugging. 5. User & Group Management Know adduser, usermod, groups. You’ll need this when configuring deployments. 6. Networking Basics Use curl, ping, netstat, ss, ip. You’ll often need to troubleshoot connectivity in cloud environments. 7. Process & Resource Monitoring Understand top, htop, ps, kill, df, du. 8. Logs & Troubleshooting Use journalctl, tail, grep, less to read logs. 9. Scripting with Bash Automate with loops, conditionals, and functions. 10.Cron Jobs Schedule tasks using crontab. Handy for maintenance, backups, and automation.

One project I would highly recommend, if you haven't done it already, is to build an HTTP web server from scratch. The server should serve static files, and as an extension, should allow you to define and serve APIs, like Flask. Use your favourite programming language, but build one from absolute scratch. It is a week-long project, but if you do it well, you will learn a ton of things, including, 1. what protocols really are and the HTTP protocol 2. writing a protocol parser - HTTP request lines and headers 3. creating TCP sockets, binding to ports, and listening for connections 4. reading and writing large data over sockets 5. how servers handle headers and the actions they take 6. handling multiple connections using threads and event loops 7. hadling different paths to serve static files 8. how to write route handlers to serve APIs Use LLMs, but make sure you understand the nuances. Trust me, you will have a great time building it, and more importantly, you will have a totally different outlook on engineering. You will stop thinking of something as blackbox and would start thinking of how X would have been implemented. If you are doing it, then all the very best, else, happy doomscrolling :)

Why is Redis So Fast and Efficient (despite being single-threaded)? 🔹 In-Memory Storage Redis keeps all data in RAM where access times are measured in nanoseconds, not milliseconds. 🔹 Single-Threaded Event Loop Redis processes commands on a single thread, avoiding locks, race conditions, and context switches. Thanks to I/O multiplexing, it efficiently handles thousands of concurrent client connections using an event loop. 🔹 Optimized Data Structures Redis provides specialized implementations of lists, sets, sorted sets and hashes optimized for both performance and memory efficiency. 🔹 I/O Efficiency Redis uses a lightweight text-based protocol called RESP to handle network I/O, and supports pipelining, allowing clients to send multiple commands in a single request. 🔹 Server-Side Scripting Redis's Lua scripting engine lets you execute complex multi-step operations atomically on the server, eliminating network roundtrips. Read the full article here: blog.algomaster.io/p/why-is-redis… Subscribe for more such articles.