🆔 abcdefghiloveukimhanbin

FULL TIME ID ONLY!!!

[🆔 abcdefghiloveukimhanbin @jhen1391]

What’s the beef between 🆔s and Cortis fans?

[chelle @hanbinblaze]

tw // suicide

MotMal's described how at his lowest time of his life, when he got no more money & attempted to end his life, he got lucky to be credited in Love Scenario. Through royalties money, his life continues.

@shxx131bi131, you saved a life by crediting someone properly..

[🆔 제슬린 🎡 @jeslyn131cosmos]

Hanbin ah… I’m so happy to see your face again. It’s been more than four months since you enlisted. ㅠㅠ
I missed you so much. I hope you have the best time at the BND’s concert!! 🩵🩶🖤

[Leslie Williams @shugarDadddy]

Before you launch your vibe coded project, run this prompt first:

“Perform a comprehensive audit of the application, covering security, reliability, concurrency, accessibility, and UI consistency.

Review the relevant codebase, architecture, data flows, API interactions, authentication and authorization logic, state management, async operations, error handling, and user-facing interfaces. Trace important flows end-to-end rather than reviewing files in isolation.

Specifically investigate:

Security vulnerabilities and data exposure
- Authentication and authorization flaws, including missing server-side permission checks, privilege escalation, insecure direct object references, and cross-tenant data access.

- Sensitive information exposed through client-side code, environment variables, API responses, logs, analytics, URLs, local storage, session storage, cookies, error messages, or source maps.

- Injection risks, including SQL, command, template, prompt, HTML, and script injection where applicable.
XSS, CSRF, SSRF, insecure redirects, unsafe file uploads, path traversal, weak session handling, insecure token storage, and missing security boundaries.

- Overly permissive database rules, API endpoints, CORS policies, storage buckets, webhook handlers, or third-party integrations.

- Secrets, API keys, credentials, internal endpoints, personal data, or implementation details that could be unintentionally exposed.

- Missing validation and sanitisation at trust boundaries. Do not assume client-side validation is sufficient.

Race conditions, concurrency, and state integrity

- Duplicate submissions caused by repeated clicks, retries, refreshes, or concurrent requests.

- Non-idempotent operations that can create duplicate records, payments, messages, bookings, jobs, or side effects.

- Stale state, optimistic update failures, lost updates, conflicting writes, and out-of-order async responses.

- Effects, subscriptions, listeners, timers, and requests that are not correctly cleaned up.

- UI states where actions remain available while an operation is already in progress.

- Cache invalidation problems and inconsistencies between client state, server state, and persisted data.

- Multi-tab, multi-device, and poor-network scenarios where relevant.

Reliability and failure handling
- Unhandled promise rejections, swallowed errors, silent failures, infinite loading states, broken retry loops, and incomplete rollback behaviour.

- Missing loading, empty, error, offline, timeout, and partial-success states.

- Failure paths that leave data or the UI in an inconsistent state.

- Assumptions about API responses, nullability, ordering, timing, or network availability that could cause production failures.

- Memory leaks, unnecessary rerenders, expensive operations, and obvious performance bottlenecks that materially affect the user experience.

Accessibility
- Semantic HTML and correct use of landmarks, headings, labels, lists, tables, buttons, and links.

- Keyboard navigation, logical tab order, focus visibility, focus trapping, and focus restoration.

- Missing or incorrect accessible names, labels, descriptions, and ARIA attributes.

- Colour contrast, text legibility, touch-target sizes, zoom behaviour, reduced-motion support, and reliance on colour alone to communicate meaning.

- Screen-reader behaviour for modals, menus, dropdowns, tabs, toasts, validation errors, loading states, and dynamically updated content.

- Forms with unclear instructions, inaccessible validation, missing autocomplete attributes, or poor error recovery.

- Test against WCAG 2.2 AA expectations where applicable.

Visual and interaction consistency
- Inconsistent spacing, typography, colour usage, border radii, shadows, icon sizing, alignment, component dimensions, and responsive behaviour.

- Components that visually appear identical but behave differently, or behave identically but are implemented inconsistently.

1/2

[🇺‌ 🇳‌ 🇴‌ 🤓 @_MIGZ29]

ᴀɴɢ ɢᴀɴᴅᴀ ɴᴜɴɢ sɪɴᴀʙɪ ɴɪ ᴄᴏɴɢ ʟᴜɪsᴛʀᴏ.

"ᴛʜᴇ ᴘʀᴏsᴇᴄᴜᴛɪᴏɴ ᴡɪʟʟ ᴘʀᴇsᴇɴᴛ ᴇxᴀᴄᴛʟʏ ᴡʜᴀᴛ ᴛʜᴇ ᴄᴏɴsᴛɪᴛᴜᴛɪᴏɴ ʀᴇᴏ̨ᴜɪʀᴇs. ᴇᴠɪᴅᴇɴᴄᴇ, ʜɪɴᴅɪ ᴛsɪsᴍɪs. ʜɪɴᴅɪ ʜᴀᴋᴀ-ʜᴀᴋᴀ. ʜɪɴᴅɪ ᴘʀᴏᴘᴀɢᴀɴᴅᴀ. ᴀᴛ ʟᴀʟᴏɴɢ ʜɪɴᴅɪ sᴏ��ᴍᴇᴅ ɴᴀʀʀᴀᴛɪᴠᴇ."

🎯🎯🎯🔥🔥🔥

[Arcane Ai @Arcane_Aii]

🚨 SOMEONE JUST BUILT a Claude Code skill called /brag that turns any side project into a fire ~20-second launch video in seconds

You just tell Claude “hey, let’s /brag about this” and it instantly generates a polished trailer — complete with music, smooth motion, sound effects, and ready-to-share copy.

No more “I built something cool” posts with static screenshots that get buried. This actually makes your project look professional and shareable without spending hours editing.

It runs on HyperFrames (HeyGen’s open-source HTML-to-video engine), comes with multiple style presets, and the creator even added demos for fake projects so you can test it right away.

This feels like one of those “why didn’t I think of this” tools that every indie hacker and builder is going to start using for launches.

Free. Open source. Stupidly easy.

Who’s trying this on their next project? 🔥

[🆔 abcdefghiloveukimhanbin @jhen1391]

@annecurtissmith Robinsons Galleria have a designated area where you can drop old gadgets even plastic bottles and I think their recent one are the sachets

[❖ ken｜旅するデザイナー @ken_tbdz]

Webサイトを最速でFigmaに取り込む方法見つけた。

Figmaの公式Chrome拡張機能を使って、キャプチャするだけ。

Claude Codeとの連携も、定番の html to design のプラグインも不要。

ページ全体はもちろん、要素単位でも取り込めます���
レイヤーとして取り込めてもちろん編集も可。しかも速い。

[🆔 abcdefghiloveukimhanbin @jhen1391]

@shashpicious_ I used to like how we create design system in Figma then attached it to Make, but after make create a separate creation of Design system and I cannot attached or do the same workflow I did before I dropped Figma Make and continue with Claude.

[🆔 abcdefghiloveukimhanbin @jhen1391]

Insightful

[Zeb Evans @DJ_CURFEW]

Today we reduced headcount by 22%. The business is the strongest it's ever been. So I think it's important to be direct about what I'm seeing and why.

First, I made this decision and I own it. I did it because the way to operate at the highest level of productivity is changing, and to win the future, ClickUp needs to change with it.

Second, this wasn't about cutting costs. Most savings from this change will flow directly back into the people who stay. We'll be introducing million-dollar salary bands. If you create outsized impact using AI, you'll be paid outside of traditional bands.

Most importantly, I have the deepest gratitude for those affected. We're doing this from a position of strength specifically so we can take care of people properly. Everyone affected receives a package aimed at honoring their contributions and easing the transition.

I only see two options: wait for this to play out gradually in the market or be honest about what I'm seeing and act proactively.

THE 100X ORGANIZATION
The primary change is that we're restructuring around what I call 100x org. The goal is 100x output. The roles required to build at the highest level are fundamentally different than they were a year ago.

Incremental improvements to existing systems won't get us there. We need new ones. That means creating enough disruption to rebuild rather than iterate on what's already broken.

The common narrative is that AI makes everyone more productive. It doesn't. Many of the workflows of today, if left unchanged, create bottlenecks in AI systems.

These roles will evolve. But waiting for that to happen naturally means falling behind now.

The 100x org is actually heavily dependent on people - infinitely more than today. This is only possible with 10x people that have embraced and adopted new ways of working.

THE BUILDERS, AGENT MANAGERS, AND FRONT-LINERS

— THE BUILDERS: 10X ENGINEERS
I don't think most companies have internalized what's actually happening with AI in engineering. The common narrative is that AI makes all engineers more productive. That may be true in isolation, but at an organization level - that is the farthest thing from reality.

Here's what we've validated recently at ClickUp: the great engineers, the ones who can orchestrate, architect, and review, are becoming 100x engineers. They're not writing code. They're directing agents that write code. The skill is judgment.

AI makes the best engineers wildly more productive, and everyone else using AI slows these engineers down.
Think about it - the bottlenecks are (1) orchestration - telling AI what to do, and (2) reviewing - what AI did. Everything is leapfrogged and no longer needed.
So who do you want orchestrating and reviewing code?

And how do you want your best engineers to spend their time?

If your best engineers are spending time reviewing other people's code, then this is inherently an inefficient bottleneck. These engineers can review their agent's code much faster than reviewing human code.

The new world is about enabling your 10x engineers to become 100x.

The wrong strategy is to push every engineer to use infinite tokens. Companies doing this are celebrating 500% more pull requests. But customer outcomes don't match the volume of code being generated.

I call this the great reckoning of AI coding, and every company will face this soon if not already.

More code is just another bottleneck to the best engineers, and ultimately to your company's impact as well.

— THE BUILDERS: 10X PRODUCT MANAGERS
Product management and design roles are merging.

Designers that have customer focus, become more like product managers.

And product managers that have intuition for UX become more like designers.

The bottleneck of user research is gone. It takes us just one mention of an agent to kickoff research and analyze results.

The bottleneck of product <> design iteration is also gone. The product builder iterates on their own, along with agents and skills that ensure alignment with quality and strategy.

Also controversial today - I believe that the wrong strategy is to have your PMs shipping code - that just introduces another bottleneck that the best engineers will waste their time on.

To be clear, PMs should be coding but they should do this in a playground to iterate, validate, and scope. That code should not go to production.

Everything outside of managing systems, orchestrating AI, and reviewing output becomes a bottleneck.
That's why the other roles that are critical along with these are the systems managers (to reduce bottlenecks) along with a bottleneck you can't replace - customer meeting time.

— THE SYSTEM MANAGERS
Ironically, the people that automate their jobs with AI will always have a job. They become owners of the AI systems - agent managers. We have many examples of these people at ClickUp.

The underlying systems in which we operate are absolutely critical to get right. I think most companies are delusional to think they can iterate on existing systems and compete in this new world.

You must create enough disruption so that old systems are deprecated entirely. If there's any definition for 'AI native' that's what it is.

— THE FRONT-LINERS
In a world that will become saturated with AI communication, the human touch will matter more than anything to customers.

This is a bottleneck that you shouldn't replace - even when agents are high enough quality to do video meetings.

One-on-one meeting time with customers is something that shouldn't be automated. The systems around the meetings should be - so that front-liners spend nearly 100% of their time with customers.

REWARDING 100X IMPACT
In a world where companies are able to do so much more with less, where does that excess money go?
In our case, much of the savings in this new operating model will flow directly back to those that enabled it.

We must reward people that create productivity accordingly. This aligns incentives on both sides. Plus, in a world where your best people create 100x impact, you can't afford to lose them.

You should aim to retain these employees for decades. The context they have and their ability to efficiently orchestrate and review will be nearly impossible to replace.

Compensation bands of today should be thrown out the door. We're introducing $1 million cash/year salary bands with a path available to nearly everyone in the company if they produce 100x impact by creating or managing AI systems.

THE FUTURE
Nearly every company will make changes like these. The ones that do it proactively will define what comes next.

The future is not fewer people. It's different work, new roles, and better rewards for those who embrace it. We're already seeing entirely new roles emerge, like Agent Managers, that didn't exist a year ago.

ClickUp is positioning to lead this shift, not just internally, but for our customers too. I've never been more certain about where we're headed.

[dodol @131chk]

Being your fan isn’t just a phase for me.

[Mario Nawfal @MarioNawfal]

🇵🇭 Police in the Philippines rode a city bus through a dedicated lane, watched as cars and motorcycles illegally tailed it to skip traffic, then stepped off at the end and ticketed every single one.

They didn't even stand a chance ☠️😂

[스태이위드한빈 @stay_withhanbin]

Missed B.I’s updates last time?

Make sure to register and join B.I Official Community in B.Stage to stay updated!

https://t.co/Afbw1RBeEh

[🆔𝚛𝚎𝚎 @tbvhanbin]

HANBIN PLEASE 😭

" How is the world without me? "

[비아이131 @B_ID22]

he is so annoying 😂#비아이

[🆔 JJIN_131 @jjin_0717]

그래..잘지내고 있다니 그거면 됐다🫳

[🆔 abcdefghiloveukimhanbin @jhen1391]

WTS: Iphone 16promax 256gb 100% battery health 188cycles (50K)

Reason: Need urgent funds
Location: Metro Manila

#iphone16promax #selling #iphone

[🆔 𝐭𝐭𝐭𝐨𝐩𝟏𝟑𝟏 🌕 @tttop131kon]

WOOSUNG: "Big shout out to B.I, BOL4, New Vaticans for being in the album. Check all those 3 artists out! They are great amazing artists that I respect so much &amp; as u can tell they're great at what they do.. We gotta hear B.I's pt"

© Crush On For The Rose
#HANBIN #비아이 #김한빈

[Khairallah AL-Awady @eng_khairallah1]

🚨 Anthropic's own team just showed how to actually prompt Claude.

24 minutes. free. from the people who built it.

watch the workshop. bookmark it.

worth more than every $300 course you almost bought.

you've been using Claude without knowing 40 of its prompts.

Then read the guide below.