Jesse

Comfort. Familiarity. Security. The need to feel safe, without realizing that most of the dangers your mind invents are unlikely to ever arrive. And even if they did, they would be far easier to face in real time than in imagination. Rejection turns into humiliation. Failure becomes permanent ruin. Conflict feels like irreversible loss. These imagined endings feel so real that anxiety seems justified, and avoidance starts to look like wisdom. You tell yourself you are being careful. Thoughtful. Strategic. We create threats that may never exist, rehearse them until they feel inevitable, and then shape our lives around avoiding them. The strange part is that if any of it actually happened, you would deal with it. You would react. Adapt. Get through it. Reality forces movement. Imagination lets fear expand without limits. Maybe we are not addicted to safety itself. Maybe we are addicted to not being disturbed, to a life where nothing unsettles us, even if that means nothing truly changes us.

there are three cycles of patterns. pattern recognition: if you want to create the life you desire, you need pattern recognition and seasons are great patterns. pattern utilization: it’s not just about recognizing patterns but using them. you need to understand what season you are in and what to do in that season. pattern creation: you have recognized so many patterns and used them. at this point, you become the pattern creator once you create your own patterns, you bring something that has never been there before and once you do that, your value goes through the roof. lastly, what overcomes fear is pattern recognition. If you have seen the pattern before, you can overcome it.

TRAINING FREQUENCY BEATS TRAINING INTENSITY Most people are wasting their time in the gym. They show up, destroy themselves for an hour, then wait days to recover. This is backwards. Strength is a skill. Not a punishment. Not a test of pain tolerance. A skill you practice like shooting a bow or playing piano. Soviet researchers in the 1950s measured electrical activity in weightlifters' muscles. As lifters got stronger over months, the EMG readings dropped. They were lifting the same weights with less neural effort. The nervous system became more efficient. Hypertrophy couldn't explain this because these athletes were doing doubles and triples, not bodybuilding volume. Every time you activate a neural pathway, that connection strengthens. Use it repeatedly and it becomes a superconductor. You don't try harder to lift the same weight. You try the same amount and lift more. You get stronger because the neural pathways become more efficient. You get bigger because volume drives growth when the load is sufficient. Both happen simultaneously without the traditional recovery debt. This works at home better than in a gym. Keep a kettlebell under your desk. Press it between tasks. Install a pull-up bar. Do a few reps every time you walk past. The equipment becomes part of your environment, not a destination you drive to. The traditional model is mass practice. Cramming. Study all night for an exam, pass, forget everything three days later. Spaced practice is writing vocabulary words on cards and reviewing them in random moments throughout your day. One builds temporary performance. The other builds permanent skill. More than a thousand papers published since the 19th century confirm spaced practice beats massed practice. Education ignores this. Strength training ignores this. You don't have to. I promise this is by far the easiest and most effective way to cause radical changes in your body composition, your posture, and even in the way you see the world or interact with it. It works for everyone. There is no minimum ability test.

You are capable of becoming way more skilled than you think. So don't get lazy, don't make excuses, don't waste your time looking for hacks to succeed without skill. Just do the damn work, work smart (efficiency) and hard (volume), and reap the reward. You have so much potential, even if you don't think so yourself. Just get the ball rolling on your skill-building, stick with it seriously and consistently for months. You will begin to see yourself transform, and you will begin to understand that you have lots of potential.

I've always worked on phone pouch art 🖌️

Advice for entry-level software engineers: Focus on understanding how computers work. Learn how they transmit, process, and store data. Fundamentals are more important than the latest frameworks. Right now, AI can generate code, but it cannot solve the problem for you. To effectively instruct the tool, you must understand the building blocks. 1. Start with Networking. Don't just verify that an API works. Understand how the data gets there. - HTTP/HTTPS: Learn the request lifecycle. - DNS: How names become IP addresses. - TCP vs. UDP: Reliability vs. Speed. If you don't understand the transport, you can't debug the latency. 2. Master the Operating System, specifically Linux. Most of the cloud runs on Linux. You need to be comfortable in the terminal. - File Systems: Everything is a file. - Process Management: How programs start, run, and die. - Memory Management: Stack vs. Heap. All code needs an OS to run. 3. Understand Data Structures (and when to use them). This isn't about passing interview tests; it's about performance. - Know why a Hash Map is faster than an Array for lookups. - Understand Big O notation to predict how your code behaves as user traffic grows. Inefficient code costs money. 4. Deep dive into Databases. Storing data is easy; retrieving it quickly is the hard part. - Indexing: How to make queries fast. - ACID: Understanding transaction integrity. - Normalization: How to structure data to avoid redundancy. Bad schema design creates tech debt that is painful to fix later. The best engineers I know aren't the ones who know every syntax of a new language. They are the ones who can understand systems thinking & can visualize the path of a byte from the user's click to the hard drive and back. “Vision without systems thinking ends up painting lovely pictures of the future with no deep understanding of the forces that must be mastered to move from here to there. — Peter Senge, The Fifth Discipline (Currency)” Focus on the mechanics, and the tools will make sense. Happy New Year, May the force be with you!

this is all you got. one life. one body. one shot to see how far you can actually go. so take the chances. take all of them. risk the embarrassment. risk the failure. risk looking foolish in pursuit of something that matters. playing it safe gets you nothing worth having. swing for the fences. bet on yourself. go all in on the thing that terrifies you. leave it all out there. every ounce of effort. every bit of energy. every piece of yourself. because you don’t get another round. this is it. so dance when you feel like dancing. work until your hands shake. play like you’re ten again. love so hard it scares you. cry when you need to cry. suffer on purpose to find out what you’re made of. push yourself into the fire to see what comes out the other side. make a name. make an impact. make something that outlives you. because you’re here once. and burn this one life down to nothing in pursuit of everything.

To EVERYONE, including all haters and losers, HAPPY NEW YEAR. Work hard, be smart and always remember, WINNING TAKES CARE OF EVERYTHING!

This is especially true in software development industry. You can’t undo a slow start, a bad first job, or a few years spent in a sloppy codebase with no mentorship. You can’t rewind the time you didn’t learn data structures, didn’t read design docs, or didn’t push yourself technically. That part is gone. But software has a unique property: future performance can completely dominate past mistakes if you get serious. I’ve seen people “waste” their first 3–5 years in service-based orgs, doing ticket work, copy-pasting code, and barely understanding the systems they touched. On paper, that looks like a dead end. In reality, some of those same people later locked in, taught themselves fundamentals, built real systems, took risks and today they’re running startups, leading teams, or operating at a level that would surprise anyone who knew their early career. What changed wasn’t luck. It was focus. They stopped obsessing over how far behind they were and started obsessing over what they could do this week. Reading one good engineering blog a day. Fixing one real bug properly instead of hacking around it. Rewriting something they didn’t understand until they did. Building side projects that forced them to learn databases, concurrency, deployment, failure modes. Slowly, consistently, without drama. Dwelling on the past is expensive in this field. It steals the only thing that actually matters: your ability to compound skill. Software rewards people who can build momentum late more than it rewards people who started early but coasted. You don’t need to be perfect. You need to be relentless and forward-looking. The present is where leverage lives. The future is where the payoff shows up. The past is just a lesson - use it, then drop it.

Winning in 2026 should be easy. 2025 already set up the blueprint. All you have to do is recognize the pattern. The blueprint: 1.Outwork yesterday. Small daily edges beat one-time heroics. 2.Make something useful before you ask for applause. 3. Fail fast, learn faster, failure without learning is just being a failure. 4.Choose long-term advantage over short-term validation. 5.Stack 1% improvements, compound them relentlessly. 6.Decide today for the version of you you want next year. 7.Protect your attention like it’s scarce currency, because it is, especially in 2026. 8. Build feedback loops: try, measure, fix, repeat. 9.Guard your mornings, the first 90 minutes set the whole day. 10.Invest in people who outgrow you; they’ll return the favor. 11.Think in systems, not episodes, solve causes, not symptoms. 12.Create value first; income follows value honestly earned. 13.Make discomfort your teacher — growth hides there. 14. Read more than you scroll; ideas compound like interest. 15.Own your reputation, it’s your most portable asset. 16.Ask dumb questions, curiosity beats pretending you know. 17. Be boringly consistent; intensity without duration is theater. 18.Spend time where leverage lives: skills, networks, and capital. 19.Teach what you learn, explaining is the fastest way to master. 20.Treat discipline as creativity’s infrastructure, not punishment. Wins don’t have to be flashy; they just have to satisfy you. Chasing public validation kills the progress of doing the work that actually matter.

Christmas time is that time to reflect and ask yourself what you really want. What truly fulfills? Christmas is a reminder of Jesus and the free gift of forgiveness only he can offer. Reflecting on this reminds me of all I have went through And how he has brought me through it all. Letting go resentment is hard but when Jesus reveals hisself as willing and able, it’s hard to deny him. Hope wherever you are you can lean into this love that meets us exactly where we are no matter what.

there must be an opposite of suicide, where someone suddenly and radically decides to start living, and rescues their own life from meaninglessness.

@AvinashSingh_20 Kotlin

Name a topic, and I'll share the best GitHub repository to learn it!

@AjeboDanny A Ddj grv-6 controller

What do you want for Christmas?

@plutomaniapopi All I want for Christmas is a Dj controller to mix all the songs you’ve ever made Santa plutoooo🧎🧎

Santa pluto is Online

@dillon_mulroy What of Kotlin? Does this apply?

if you're trying to break into software dev, learn java and spring then apply to every company you've never heard of on the fortune 500 list

In your 20s you will be tempted to prove that you’re doing well, it’s important you resist performing for an audience that isn’t watching.

Go take the State of React 2025 survey if you have a minute! survey.devographics.com/survey/state-o…