Pray for Asian Paints taking support in the middle and bouncing back above the Right shoulder else the target of 2550 is open now.

This breakdown has come below 200 DMA

How to create a freelancing website that makes money.

Everything I've learned.

A thread.

As a freelancer,

Your website is everything.

First, prioritise its existence.

Second, prioritise its improvement.

The technology you use is irrelevant.

- WordPress
- Notion
- Carrd
- Wix

It doesn't matter which you choose,

What matters is you have a website.

Pick a platform that you're comfortable with.

If you can:

- Capture leads
- Add content easily
- Have a clear design

You're good.

If your website doesn't get leads,

It's not working.

Don't rest on a website that doesn't work for you.

Improve it until it does.

THREAD: Meditations on marriage metaphors in Ruth

The book of Ruth is, of course, a story about a beautiful marriage. But even before the courtship and the wedding and the important genealogy at the end, we find interesting language that is strikingly reminiscent of Genesis 2:24

That important verse reads:

'Therefore a man shall leave [יַֽעֲזָב] his father and his mother and hold fast [וְדָבַ֣ק] to his wife, and they shall become one flesh.'

The verb עזב can be quite strong in force. For example, Joseph leaves behind [וַיַּעֲזֹ֤ב] his garment as he flees from Pharaoh's wife's sexual advances. Countless times, Israel is depicted abandoning the LORD, for example in Judg 2:12 [וַיַּעַזְב֞וּ], and going after other gods.

Likewise, the verb דבק is rather striking. Lot is mortified of disaster overtaking him [תִּדְבָּקַ֥נִי] as he flees from Sodom. Israel is commanded in Deut 10:20 to cling fast [תִדְבָּ֔ק] to the LORD and serve him and swear by his name.

Together they illustrate how radical God designed marriage to be. Marriage is a real severing of family relations in order to form a new, permanent bond with another human being.

Something very similar to this takes places in Ruth's life.

A thread on HN about bad code in legacy projects both makes me think how little we've learned as a discipline over the years and, honestly, how little credit we give ourselves for some pretty major

Fun going down this list and thinking: "Hmm, plausible at a well-run modern software shop", "Hmm, possible, but requires implausible tradeoffs", "Literally disallowed by languages", and "If you were to attempt doing that our test suite wouldn't let you merge."

I think we as an industry celebrate (not quite the right word) failure too much and don't celebrate success nearly enough. There is no DailyWTF for competent execution, word of which generally stays pretty local to the source while incompetence passes into legend.

Alrighty let me try to thread the needle on being the change I want to see in the world while not giving away anything that will get me in trouble:

Ruby has wonderful developer ergonomics. Typed languages are easier for machines to guarantee the correctness of. We built a type checker for Ruby (and I believe it is slated for OSS release sometime).

c.f.