Jirawat Uttayaya @JavaJirawat

ABC: Always Be Coding javajirawat.com Boston, MA Joined November 2013

Tweets

448
Followers

192
Following

2K
Likes

3K

Jirawat Uttayaya @JavaJirawat

a year ago

0 0 0 18 0

View Details

Boston Public Works @BostonPWD

2 years ago

With the forecast calling for snow to fall through midnight (additional 2 - 3 inches), PWD crews & contractors continue to treat & clear #BostonStreets. If possible, please stay off the roads so we can operate our equipment at a safe distance. To report an issue, contact @BOS311

7 11 36 8K 1

View Details

Bret Taylor @btaylor

2 years ago

@zack_overflow At one point Google Maps had a fully functional XSL transform engine written in JavaScript to translate XML from the server to the content you saw on the screen. It was insane.

20 51 1K 113K 173

View Details

Nature is Amazing ☘️ @AMAZlNGNATURE

2 years ago

Explain this!

2K 7K 124K 24.9M 14K

View Details

Netflix @netflix

2 years ago

Grave of the Fireflies, a Studio Ghibli classic, is coming to Netflix on September 16. Based on Akiyuki Nosaka's short story and directed by Isao Takahata, orphaned siblings Seita and Setsuko fight for survival amidst the devastation in post-war Japan.

246 1K 7K 1.7M 895

View Details

Jirawat Uttayaya @JavaJirawat

2 years ago

The contractors couldn’t even remodel my kitchen on-time or on-budget. It seemed like they just gave me a date and dollar amount that I wanted to hear so I would agree to start the project. In that sense, housing construction and software engineering are alike.

Igor Bespalchuk @IBespalchuk

2 years ago

@allenholub Have you ever built a house? Was it important for you to complete in a year or in 3 years? So simple and obvious example - would you fight against it as well, might be insisting that software is completely different?

5 0 1 20K 0

0 0 0 50 0

View Details

Jirawat Uttayaya @JavaJirawat

2 years ago

@tunguz Cmon we all know tech conferences were just an excuse to party on the company’s dime.

0 0 0 12 0

View Details

Jirawat Uttayaya @JavaJirawat

2 years ago

@AaronErickson @mipsytipsy @AaronErickson Agree 100% To anyone that disagrees, would you trust and hire a successful computer EM to manage building a bridge. An EM needs to understand what they are managing.

0 0 1 44 0

View Details

Only In Boston @OnlyInBOS

2 years ago

Good morning from Boston. 💚

55 2K 12K 275K 453

View Details

Barack Obama @BarackObama

2 years ago

Congrats to the new champs, the Boston @Celtics! 18 titles is no easy feat – well deserved.

NBA @NBA

2 years ago

The @celtics are the 2023-24 NBA Champions!

2K 33K 112K 45.7M 2K

4K 22K 301K 40.0M 2K

View Details

Boston Celtics @celtics

2 years ago

BANG

432 7K 28K 1.4M 944

View Details

Blake Emal @heyblake

2 years ago

Found this gem a while back. 7 novel & valuable sales tips:

18 286 2K 631K 4K

View Details

Ashish Pratap Singh @ashishps_1

2 years ago

15 of the most common tradeoffs in System Design: 1. 𝐒𝐜𝐚𝐥𝐚𝐛𝐢𝐥𝐢𝐭𝐲 𝐯𝐬. 𝐏𝐞𝐫𝐟𝐨𝐫𝐦𝐚𝐧𝐜𝐞: Grow the system to handle more work vs. execute tasks faster. 2. 𝐕𝐞𝐫𝐭𝐢𝐜𝐚𝐥 𝐯𝐬. 𝐇𝐨𝐫𝐢𝐳𝐨𝐧𝐭𝐚𝐥 𝐒𝐜𝐚𝐥𝐢𝐧𝐠: Scale up with more powerful hardware vs. scale out by adding more servers. 3. 𝐋𝐚𝐭𝐞𝐧𝐜𝐲 𝐯𝐬. 𝐓𝐡𝐫𝐨𝐮𝐠𝐡𝐩𝐮𝐭: Prioritize fast responses for individual tasks vs. maximize the number of tasks over time. 4. 𝐒𝐐𝐋 𝐯𝐬 𝐍𝐨𝐒𝐐𝐋 𝐃𝐚𝐭𝐚𝐛𝐚𝐬𝐞𝐬: Opt for structured data and strict schemas vs. embrace flexibility and scalability for varied data types. 5. 𝐂𝐨𝐧𝐬𝐢𝐬𝐭𝐞𝐧𝐜𝐲 𝐯𝐬. 𝐀𝐯𝐚𝐢𝐥𝐚𝐛𝐢𝐥𝐢𝐭𝐲 (𝐂𝐀𝐏 𝐓𝐡𝐞𝐨𝐫𝐞𝐦): Guarantee up-to-date data everywhere vs. ensure system is always up. 6. 𝐒𝐭𝐫𝐨𝐧𝐠 𝐯𝐬 𝐄𝐯𝐞𝐧𝐭𝐮𝐚𝐥 𝐂𝐨𝐧𝐬𝐢𝐬𝐭𝐞𝐧𝐜𝐲: Need immediate data accuracy across all nodes vs. is a short delay acceptable for system availability? 7. 𝐑𝐞𝐚𝐝-𝐓𝐡𝐫𝐨𝐮𝐠𝐡 𝐯𝐬 𝐖𝐫𝐢𝐭𝐞-𝐓𝐡𝐫𝐨𝐮𝐠𝐡 𝐂𝐚𝐜𝐡𝐞: Fetch and cache data upon request, or write data to cache and database simultaneously for consistency. 8. 𝐒𝐲𝐧𝐜𝐡𝐫𝐨𝐧𝐨𝐮𝐬 𝐯𝐬. 𝐀𝐬𝐲𝐧𝐜𝐡𝐫𝐨𝐧𝐨𝐮𝐬 𝐏𝐫𝐨𝐜𝐞𝐬𝐬𝐢𝐧𝐠: Wait for each task to complete vs. move on and handle tasks as they finish. 9. 𝐁𝐚𝐭𝐜𝐡 𝐯𝐬 𝐒𝐭𝐫𝐞𝐚𝐦 𝐏𝐫𝐨𝐜𝐞𝐬𝐬𝐢𝐧𝐠: Process data in chunks vs. handle it in real-time as it arrives. 10. 𝐒𝐭𝐚𝐭𝐞𝐟𝐮𝐥 𝐯𝐬 𝐒𝐭𝐚𝐭𝐞𝐥𝐞𝐬𝐬 𝐀𝐫𝐜𝐡𝐢𝐭𝐞𝐜𝐭𝐮𝐫𝐞: Remember user sessions and data vs. treat each request as independent. 11. 𝐋𝐨𝐧𝐠 𝐏𝐨𝐥𝐥𝐢𝐧𝐠 𝐯𝐬 𝐖𝐞𝐛𝐒𝐨𝐜𝐤𝐞𝐭𝐬: Request waits for data vs. continuous two-way connection. 12. 𝐍𝐨𝐫𝐦𝐚𝐥𝐢𝐳𝐚𝐭𝐢𝐨𝐧 𝐯𝐬. 𝐃𝐞𝐧𝐨𝐫𝐦𝐚𝐥𝐢𝐳𝐚𝐭𝐢𝐨𝐧: Organize data to eliminate duplication vs. combine for faster reads at the cost of some redundancy. 13. 𝐌𝐨𝐧𝐨𝐥𝐢𝐭𝐡𝐢𝐜 𝐯𝐬. 𝐌𝐢𝐜𝐫𝐨𝐬𝐞𝐫𝐯𝐢𝐜𝐞𝐬 𝐀𝐫𝐜𝐡𝐢𝐭𝐞𝐜𝐭𝐮𝐫𝐞: Build a single, unified application vs. develop a collection of independent, smaller services. 14. 𝐓𝐂𝐏 𝐯𝐬. 𝐔𝐃𝐏: Guarantee reliable and ordered data delivery vs. opt for faster, though potentially unordered, transmission. 15. 𝐑𝐄𝐒𝐓 𝐯𝐬. 𝐆𝐫𝐚𝐩𝐡𝐐𝐋: Use standard HTTP methods for data exchange vs. query precisely what you need from a single endpoint. ♻️ Repost to help others in your network. Join 11,901+ readers of my free newsletter (Dev Design Digest) to master coding and system design: newsletter.ashishps.com

1 106 470 27K 438

View Details

MIT CSAIL @MIT_CSAIL

2 years ago

Stanford University professor Jerry Cain breaks down the C programming language, highlighting pointers and structs. He also discusses an unconventional method to access struct fields: bit.ly/3UvBKar v/@7etsuo

17 302 2K 127K 1K

View Details

Jirawat Uttayaya @JavaJirawat

3 years ago

A wise philosopher once said: "I don't care what you say anymore, this is my life Go ahead with your own life and leave me alone"

Mitchell Hashimoto @mitchellh

3 years ago

One thing that always used to frustrate me in my 20s is when other people would tell me I should have better work/life balance. Like, look, I'm not preaching the way you should balance your life so don't judge me for the way I choose to balance mine.