What is Hackers' Pub?

Hackers' Pub is a place for software engineers to share their knowledge and experience with each other. It's also an ActivityPub-enabled social network, so you can follow your favorite hackers in the fediverse and get their latest posts in your feed.

0
1
0
0
1
1
0

バラクラバ流行った時も思ったけど、頭まわりの流行は思い切って乗ってみると楽しいよ!
スカーフ頭に巻いてると、可愛いけど私には出来ない、似合わないって言う人いるんだけど、巻いてみたいならぜひ巻いてみてほしい。ロマンチックで素敵だから!!!
シルクのものが古着屋で安く買えるしね。

0
0
0
1

バラクラバ流行った時も思ったけど、頭まわりの流行は思い切って乗ってみると楽しいよ!
スカーフ頭に巻いてると、可愛いけど私には出来ない、似合わないって言う人いるんだけど、巻いてみたいならぜひ巻いてみてほしい。ロマンチックで素敵だから!!!
シルクのものが古着屋で安く買えるしね。

0
0
0
0
0
1
1
1
0
0
1

For my library and CLI projects, I've been writing documentation before writing any code. It helps me imagine the final interface early on, which usually leads to better design. Sure, sometimes I miss implementation details and have to revise later, but hey—it's just docs. Docs are easy to change.

This tiny habit has surprisingly big payoffs. When I focus on how things will be used rather than how they'll be built, I end up with interfaces that actually make sense.

Anyone else do this? Curious about your experience with documentation-first approaches.



RE: https://hollo.social/@hongminhee/01964c76-ef1e-7994-b3f0-57f967742566

8
0
0
0
0
1
1
0
0
0
0
1
0
0
0
0

關於和伴侶的薪水差距

其實我和伴侶一起的前段大部分時間,有接近一半時候薪水都比我少一截,另外有幾年差不多

因為各種機緣,他去年找到一份工作,薪水暴漲三倍。雖然有時候不爽他為什麼薪水比我高、工作還沒我操。不過我知道他是用之前很多年的低薪換來的,不是他待在那家公司的經驗,他連得到現職的面試機會都很難

領多少薪水除了看能力,我覺得更多時候是看機緣,各有前因莫羨人。你要是在意另一半薪水比你高,就去進修、去研究發展職業道路,不是在那邊覺得自己低人一等

舊時代為什麼普遍認為男性薪水要比女性高,有沒有想過是女性的職場角色受限?現在水平追到貼近、或者比男性高,是不是時代進步而不是你自己退步?

如果是另一半在意的話,就思考是要配合對方,還是另覓伴侶了(拖

總之有毒男子氣慨幫不了什麼忙

0

何時に来い言うからその時間に来たのに居なかった言われて、???なんすけど 言い返すのも面倒で、はぁ…で終わらせちゃった

0

異常に絵がうまくフォロワーの少ないアカウントを見つけたときはまずメディア欄を見て投稿ペースを確認するようにしてる…
新規のフルカラーイラストを1日で3枚以上、連日投稿してたらそのアカウントは…
:blobcat_frustration:
こんな人生になりたくなかった…

1
0
0
0

For my library and CLI projects, I've been writing documentation before writing any code. It helps me imagine the final interface early on, which usually leads to better design. Sure, sometimes I miss implementation details and have to revise later, but hey—it's just docs. Docs are easy to change.

This tiny habit has surprisingly big payoffs. When I focus on how things will be used rather than how they'll be built, I end up with interfaces that actually make sense.

Anyone else do this? Curious about your experience with documentation-first approaches.



RE: https://hollo.social/@hongminhee/01964c76-ef1e-7994-b3f0-57f967742566

8

For my library and CLI projects, I've been writing documentation before writing any code. It helps me imagine the final interface early on, which usually leads to better design. Sure, sometimes I miss implementation details and have to revise later, but hey—it's just docs. Docs are easy to change.

This tiny habit has surprisingly big payoffs. When I focus on how things will be used rather than how they'll be built, I end up with interfaces that actually make sense.

Anyone else do this? Curious about your experience with documentation-first approaches.



RE: https://hollo.social/@hongminhee/01964c76-ef1e-7994-b3f0-57f967742566

8
0
0
0
0