Jessie Siat

Software Developer. True Faith.

[Jessie Siat @JessieSiat]

https://t.co/auD0lr9zAt

[Jessie Siat @JessieSiat]

@NVIDIAGeForce GeForce RTX 5090

[Shaan Puri @ShaanVP]

new one minute blog: the big lie about competition

[Caleb Porzio ⚡️ @calebporzio]

btw, clean way to get the second element in an array if you've never seen this

[Jessie Siat @JessieSiat]

TIL https://t.co/DUbvukSMXg

[Freek Van der Herten @freekmurze]

🔗 Optimizing PHP for performance (by @mateusjatenee)
https://t.co/yQa8IefKjp

[Elon Musk @elonmusk]

👌

[Adam Wathan @adamwathan]

I've shared this before but even though I agree with @thorstenball that these are the basics, I feel like they're simultaneously so uncommon that this post could be called "How to be a 10x engineer".

https://t.co/LlnPKEuXHa

[Adam Wathan @adamwathan]

Incredible post on optimizing JavaScript for performance — so many neat little surprises in here:

https://t.co/8TGr95U6Fe

[DHH @dhh]

"Strong minds discuss ideas. Average minds discuss events. Weak minds discuss people." — Socrates

[Jessie Siat @JessieSiat]

blog about AI fundamentals using AI, that is learning by writing https://t.co/wFgZSAyvzn

[Jessie Siat @JessieSiat]

@aarondfrancis @markjaquith Lol

[nunomaduro @enunomaduro]

To be clear: I have zero problems with changing my opinions about topics. I change my opinion all the time, and that does not hurt my ego. In tech, it's insanely important that your ego does not block you from progressing.

[Pascal Baljet @pascalbaljet]

In the #Laravel 4.x days, I made a prototype for a company that eventually evolved into a massive app with hundreds of classes and tons of functionality.

Today it runs on Laravel 10 and #PHP 8.2. We always upgraded to the next Laravel and PHP release.

The secret? Keep it simple:

✅ Embrace the framework. Don't fight it.
✅ Don't use too many packages.
✅ No quick fixes. Fix it properly.
✅ Tests, tests, tests.
✅ Reread the Laravel docs every now and then, even if you think you know it all.

[Santiago @svpino]

Scrum is a cancer.

I've been writing software for 25 years, and nothing renders a software team useless like Scrum does.

Some anecdotes:

1. They tried to convince me that Poker is a planning tool, not a game.

2. If you want to be more efficient, you must add process, not remove it. They had us attending the "ceremonies," a fancy name for a buttload of meetings: stand-ups, groomings, planning, retrospectives, and Scrum of Scrums. We spent more time talking than doing.

3. We prohibited laptops in meetings. We had to stand. We passed a ball around to keep everyone paying attention.

4. We spent more time estimating story points than writing software. Story points measure complexity, not time, but we had to decide how many story points fit in a sprint.

5. I had to use t-shirt sizes to estimate software.

6. We measured how much it cost to deliver one story point and then wrote contracts where clients paid for a package of "500 story points."

7. Management lost it when they found that 500 story points in one project weren't the same as 500 story points on another project. We had many meetings to fix this.

8. Imagine having a manager, a scrum master, a product owner, and a tech lead. You had to answer to all of them and none simultaneously.

9. We paid people who told us whether we were "burning down points" fast enough. Weren't story points about complexity instead of time? Never mind.

I believe in Agile, but this ain't agile.

We brought professional Scrum trainers. We paid people from our team to get certified. We tried Scrum this way and that other way. We spent years doing it.

The result was always the same: It didn't work.

Scrum is a cancer that will eat your development team. Scrum is not for developers; it's another tool for managers to feel they are in control.

But the best about Scrum are those who look you in the eye and tell you: "If it doesn't work for you, you are doing it wrong. Scrum is anything that works for your team."

Sure it is.

[Aaron Francis @aarondfrancis]

PHP doesn't suck (anymore)

🎥 I made a new video for you! I cover some of the language advances since 2012 or so. There's some fun stuff you might have missed.

https://t.co/DEzfFc7494

[Addy Osmani @addyosmani]

Tip: @ChromeDevTools can now override the content of Fetch/XHR requests! Great for mocking APIs without waiting on backend changes!

This and lots more in Chrome 117: https://t.co/kP0JrGfHlz

[Addy Osmani @addyosmani]

Write about what you learn. It pushes you to understand topics better. Sometimes knowledge gaps only become clear when explaining things to others.

[Turner Novak 🍌🧢 @TurnerNovak]

Smoothest shot I’ve ever seen

[nunomaduro @enunomaduro]

Important rule on testing: arrange, act, and assert! Always separate your test in these 3 different steps. ✅ @LaraconIN @christophrumpel