backlit bytes💡

153 posts

backlit bytes💡

backlit bytes💡

@backlitbytes

creating tiny games 🎮, web experiments 🕸️. follow me for rare, but fun posts 💎

California Katılım Ekim 2023
249 Takip Edilen56 Takipçiler
Sabitlenmiş Tweet
backlit bytes💡
backlit bytes💡@backlitbytes·
I built a Gameboy with Svelte using HTML, CSS, Javascript 🎮 There’s a few details I’d like to share….
English
1
1
5
1.9K
Ryan Dahl
Ryan Dahl@rough__sea·
I really don't want to be vegan. Because actually I have no problem with killing animals for food - it's just the way of the world. I don't even really mind torturing animals for food - as long as they're low cognition (fish, insects, etc) However - I really don't want to participate in the active (often life long) torture of high cognition animals like pigs. Chickens are pretty dumb, but I'm not down with stuffing them into small cages their whole lives to peck at each other. Not ok with dairy cow-calf separation. And the more you look into it, the more you realize that humane sources of meat, dairy, and eggs are VERY hard to come by. Buying the more expensive brand at the grocery store does not imply torture free. If you're eating bacon, an egg, cheese from a random restaurant - you are participating and enabling animal torture. These labels "vegan", "vegetarian", "pescatarian" don't work for me. A vegetarian who eats dairy and eggs still participates in torture. I would lustfully eat a steak that had a good life, or an egg from a non-factory farm. For all the daily political bullshit that happens - the torture of billions of animals is so rarely discussed.
English
48
13
302
30.4K
backlit bytes💡
backlit bytes💡@backlitbytes·
@jh3yy Claude said I don’t have it installed, where did you get it?
English
0
0
0
6
jhey ʕ•ᴥ•ʔ
the most valuable /skill you have is the ability to articulate yourself
English
9
4
136
5.8K
Kenney
Kenney@KenneyNL·
okay Godot all you need to do is skip a few versions, this is worth it
Kenney tweet media
English
49
89
3.3K
135.2K
backlit bytes💡
backlit bytes💡@backlitbytes·
@kenwheeler I’d like this, but I don’t really branch or use worktrees so when I run multiple agents on the same repo they’d likely auto commit half baked changes from other threads. Though, an auto committer could try to commit only the right files/lines to the right commit 🤔
English
0
0
0
29
patagucci perf papi
patagucci perf papi@kenwheeler·
building a thing and a generative autocommit after each conversational turn feels like the play now
English
10
1
61
4K
backlit bytes💡
backlit bytes💡@backlitbytes·
@ryanflorence I really dig it. But “handle” feels awk as a name. I guess I could call it whatever, “h” will do
English
0
0
0
167
Ryan Florence
Ryan Florence@ryanflorence·
Remix UI: 1. Build a model, a pile of functions over data, a class instance with methods, or anything else--no hooks, no signals, no state-update-coupling semantics, no wrong way to keep your state 2. Set it up in a component 3. Change it in events 4. Update the UI
Ryan Florence tweet media
English
16
7
118
13K
backlit bytes💡
backlit bytes💡@backlitbytes·
@ThePrimeagen This 100x dev cannot afford to take vacation. Each single day off is 4 months of work. Every dentist appointment is a full end to end project.
English
0
0
6
765
ThePrimeagen
ThePrimeagen@ThePrimeagen·
100x eng 3.65 work days = 1 year traditional work
ThePrimeagen tweet media
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.

English
116
78
3K
206.9K
backlit bytes💡
backlit bytes💡@backlitbytes·
@levelsio Not remotely true, look at all the games released from all sizes of studios and tell me how many could be accurately described by what you wrote. I bet less than 1% Even still, more interactive movies are worth something too
English
0
0
0
253
Thomas Brush
Thomas Brush@thomasbrushdev·
Dare you to genuinely ask Jesus to show up in your life and see what happens
English
18
5
150
7.5K
backlit bytes💡
backlit bytes💡@backlitbytes·
@Toadsanime I buy full priced for must haves or if I really love the dev. But otherwise, why would you buy full price when you know there is a deal just around the corner? Play games a little later, save like 50%. Plus you get to see if the game is really worth it or just day 1 hype
English
0
0
1
156
backlit bytes💡
backlit bytes💡@backlitbytes·
@ibuildthecloud @glcst Probably more likely that the future is hard to imagine since there is no reference for it, so everything we create as futuristic basically should look strange, and strange things would be less likely to fall into traditional gender imagery.
English
0
0
0
22
Darren Shepherd
Darren Shepherd@ibuildthecloud·
@glcst I've always been fascinated when people show futuristic things how they're always androgynous. Hunger games being like that also. But you notice in popular culture how we gravitate towards it. It's odd. Why would we think there's something admirable or better about androgyny.
English
1
0
2
275
ThePrimeagen
ThePrimeagen@ThePrimeagen·
All jokes aside * +15 direct reports is an insane number pre AI * Now coordination is harder because things can "move faster." * Now the boss should also code?? Ship features?? How is this even reasonable?
Brian Armstrong@brian_armstrong

This is an email I sent earlier today to all employees at Coinbase: Team, Today I’ve made the difficult decision to reduce the size of Coinbase by ~14%. I want to walk you through why we're doing this now, what it means for those affected, and how this positions us for the future. Why now Two forces are converging at the same time. We need to be front footed to respond to both. First, the market. Coinbase is well-capitalized, has diversified revenue streams, and is well-positioned to weather any storm. Crypto is also on the verge of the next wave of adoption, with stablecoins, prediction markets, tokenization, and more taking off. However, our business is still volatile from quarter to quarter. While we've managed through that cyclicality many times before and come out stronger on the other side, we’re currently in a down market and need to adjust our cost structure now so that we emerge from this period leaner, faster, and more efficient for our next phase of growth. Second, AI is changing how we work. Over the past year, I’ve watched engineers use AI to ship in days what used to take a team weeks. Non-technical teams are now shipping production code and many of our workflows are being automated. The pace of what's possible with a small, focused team has changed dramatically, and it's accelerating every day. All of this has led us to an inflection point, not just for Coinbase, but for every company. The biggest risk now is not taking action. We are adjusting early and deliberately to rebuild Coinbase to be lean, fast, and AI-native. We need to return to the speed and focus of our startup founding, with AI at our core. What this means To get there, we are not just reducing headcount and cutting costs, we’re fundamentally changing how we operate: rebuilding Coinbase as an intelligence, with humans around the edge aligning it. What does this mean in practice? - Fewer layers, faster decisions: We are flattening our org structure to 5 layers max below CEO/COO. Layers slow things down and create coordination tax. The future is small, high context teams that can move quickly. Leaders will own much more, with as many as 15+ direct reports. Fewer layers also means a leaner cost structure that is built to perform through all market cycles. - No pure managers: Every leader at Coinbase must also be a strong and active individual contributor. Managers should be like player-coaches, getting their hands dirty alongside their teams. - AI-native pods: We’ll be concentrating around AI-native talent who can manage fleets of agents to drive outsized impact. We’ll also be experimenting with reduced pod sizes, including “one person teams” with engineers, designers, and product managers all in one role. In short: AI is bringing a profound shift in how companies operate, and we’re reshaping Coinbase to lead in this new era. This is a new way of working, and we need to leverage AI across every facet of our jobs. To those who are affected I know there are real people behind these decisions — talented colleagues who have poured themselves into this company and our mission. To those of you who will be leaving: thank you. You’ve helped build Coinbase into what it is today, and I am sincerely grateful for everything you've done. All impacted team members will receive an email to their personal account in the next hour with more information, and an invitation to meet with an HRBP and a senior leader in your organization. Coinbase system access has been removed today. I know this feels sudden and harsh, but it is the only responsible choice given our duty to protect customer information. To those affected, we will be providing a comprehensive package to support you through this transition. US employees will receive a minimum of 16 weeks base pay (plus 2 weeks per year worked), their next equity vest, and 6 months of COBRA. Employees on a work visa will get extra transition support. Those outside of the US will receive similar support, based on local factors and subject to any consultation requirements. Coinbase prides itself on talent density. Our employees are among the most talented people in the world, and I have no doubt that your skills and experience will be highly sought after as you pursue your next chapters. How we move forward To the team that is staying, I know this is a difficult day. We’re saying goodbye to colleagues and friends you've been in the trenches with. But here’s what I want you to know as we move forward together: Over the past 13 years, we have weathered four crypto winters, gone public, and built the most trusted platform in our industry. We’ve made it this far by making hard decisions and by always staying focused on our mission. This time will be no different – nothing has changed about the long term outlook of our company or industry. And most importantly, our mission has never been more important for the world. Increasing economic freedom requires a new financial system, and we’re building it. The Coinbase that emerges from this will be more capable than ever to achieve our mission. Brian

English
158
63
2.8K
185.6K
Jonathan Blow
Jonathan Blow@Jonathan_Blow·
Secret heuristic: if you see "idk" in a tweet, stop reading. 100% accurate.
English
42
8
483
44.8K
Adam Rackis
Adam Rackis@AdamRackis·
Sorry I'm horny posting on main again
Adam Rackis tweet media
English
4
1
42
5.3K
backlit bytes💡
backlit bytes💡@backlitbytes·
@ThePrimeagen Stop, you’re going to make me go back to measuring twice and cutting once (instead of cutting 100 times and never measuring anything)
English
0
0
0
162
ThePrimeagen
ThePrimeagen@ThePrimeagen·
I really just like to program Hands on keyboard, music, deeply thinking and enjoying the process
English
244
317
4.9K
126.3K
backlit bytes💡
backlit bytes💡@backlitbytes·
@MrModez @0xVe1L I love the passion and this approach because instead of fighting to get large changes in, you can show the project the value of many large changes and inspire Godot to adopt the best updates
English
0
0
2
81
MrModez Pineapple
MrModez Pineapple@MrModez·
@0xVe1L 2) multi-scene editing required a total rewrite of how singletons work across the whole editor 3) it's my personal passion project, and every decision comes down to what i see as the best user experience 4) the editor will always be released for free!
English
3
0
19
850
MrModez Pineapple
MrModez Pineapple@MrModez·
time to reveal what i've been building. GDstudio is a new editor for Godot projects, aimed at UX improvements for productivity and speed. alpha release is fast approaching! sign up at gdstudio.dev to get a notification on the day it ships. 4 main features below ↓
MrModez Pineapple tweet media
English
13
51
550
30.3K