pawitp's profile picture. Tech Fanatics

pawitp

@pawitp

Tech Fanatics

pawitp reposted

I enjoy cleaning up messy code. It feels like the equivalent of spring cleaning for developers. Fixing names, adding structure, removing structure, deleting unnecessary code (this is the best one), and simplifying complex code.


pawitp reposted

Good software engineers have a willingness but not an eagerness to challenge others on their ideas. Some bad engineers want to challenge everything. It’s as if they’re eager to be difficult. And some bad engineers don’t want to challenge anything or rock the boat in any way.


pawitp reposted

หน่วยงานรัฐที่รู้ตัวว่าคนร้ายกำลังพยายามปลอมตัว ควรเลิกใช้โดเมน .com หรือโดเมนอื่นนอกจาก .go.th ทั้งหมดโดยเร็ว จะได้ประชาสัมพันธ์ได้ง่ายว่าให้ตรวจสอบหรือติดต่อทางใด รวมถึงอีเมลทั้งหมดที่ใช้ติดต่อประชาชน


pawitp reposted

A few "corporate" phrases commonly used in larger tech companies, what they usually mean, and what they might sometimes mean. What other phrases have you learned to translate - things that were unusual when working at e.g. smaller companies?

GergelyOrosz's tweet image. A few "corporate" phrases commonly used in larger tech companies, what they usually mean, and what they might sometimes mean.

What other phrases have you learned to translate - things that were unusual when working at e.g. smaller companies?

pawitp reposted

One of the worst feelings in software is when something doesn’t work, then magically starts and you have no idea why … It’s then, when you dive deep to figure it out when you learn the most.


Yes, I miss Gerrit. With GH, I end up having to do this manually by creating PRs on top of each other and rebasing often.

A very efficient+convenient workflow that is unbeknown/unavailable outside few large tech companies: stacked diffs. You break up your PR in several, stacked changes ready to be pushed to master. Once reviewed, they all land on master. As used at Meta, Uber & many other places.

GergelyOrosz's tweet image. A very efficient+convenient workflow that is unbeknown/unavailable outside few large tech companies: stacked diffs.

You break up your PR in several, stacked changes ready to be pushed to master. Once reviewed, they all land on master.

As used at Meta, Uber & many other places.


pawitp reposted

The "Software Engineering at Google" book is now free to read online: bit.ly/swe-book. Great insights on improving code quality & scaling engineering teams.

addyosmani's tweet image. The "Software Engineering at Google" book is now free to read online: bit.ly/swe-book. Great insights on improving code quality & scaling engineering teams.

pawitp reposted

I cannot read DD/MM/YYYY dates anymore, thanks USA. I also can't read MM/DD/YYYY either. Use YYYY-MM-DD. Please.


pawitp reposted

Hiding levels means eg every sw engineer’s title internally is “software engineer” regardless if they’re entry-level, senior or staff/ principal-level. Hidden hierarchies means you need time and connections to figure out who the principal engineers are who have a bigger say.


Loading...

Something went wrong.


Something went wrong.