mayask

Vibe coding is fun until you're processing real money. We're hiring a Staff Ruby Engineer to help us scale a payments infrastructure that can't afford to "vibe" 🧵

@KentonVarda Interestingly I hear this a lot about blue sky but it wasn't my experience at all.

Bluesky: You talk about AI, you get shouted down and scolded. X: You talk about AI, you get tons of positive replies... from AI.

Getting really tired of these reply bots.

Claude usage limits and stats just gone a few hours ago 🤔

@mbryzek It does now!

@mayask_ Odd - working for me. Reposting: cameronbryzek.com/projects/oscil…

So proud of my Cameron who built a game on an oscilloscope - details here (cameronbryzek.com/projects/oscil…) - and please upvote on news.ycombinator.com/item?id=463476… !

Nuestro día 32 amanece con lluvia, pero eso no nos asusta. Seguimos defendiendo el proyecto educativo de nuestras hijas e hijos: innovador, multidisciplinar, activo, humano. @BegonaPedrosa @Imanol_Pradales @Gob_eus @hezkuntzaEJGV #osotuonada #osotuhuelgahambre

stay grounded, keep cooking the ai hype cycle is wild, and we all feel some anxiety — every week there's some new model that's supposedly gonna change everything and everyone's scrambling to keep up but here's the thing: the fundamentals don't change. good design is still good design. solving real human problems, finding the ideal systems, making the best tools are still what matters. same with competition: know what they're building, but don't watch too closely. the anxiety comes from thinking you have to chase every trend or copy every feature or you'll get left behind. most trends are just noise. most competitor moves are just reactions to other reactions. focus on what's always been true: understand your systems and users, solve real problems, build quality stuff with care. stay grounded in your values and let the technology serve your vision, not the other way around. the best builders aren't the ones following every ai paper on twitter or obsessing over what others ship. they're the ones using whatever tools help them build the best thing for people. make your own best thing. everything else is distraction.

We’re hiring engineers again! iOS, backend, data, generalists... - Fully remote - SF based salary, no negotiation games - Challenging computer problems. Real impact - Engineering-led culture Your code will power apps like ChatGPT, VSCO, Notion and tens of thousands more.

“Remember those who did the invisible work of removing. Their legacy was not to build a sand castle, but to care for the beautiful beach on which we play.” A beautiful analogy by @kepano that we should also celebrate the efforts of those in the trenches doing the unthankful grunt work that keeps the lights on. stephango.com/remove

@owickstrom I think it is impressive that someone can do an instant 180 degree turnaround like that without carrying any of the work matters over into vacation.

It's weird to be absolutely entangled in work, then go on vacation, and suddenly switch to 100% focused on home renovation, carpentry, and reading. Same energy in a way, just another problem statement. And probably an indication that I'm not resting at all...

We've been growing fast lately, and we're growing the Ghost team to keep up! Still looking for more staff-level product engineers to come and work with us full-time on open source:

Want to help shape the future of billing for developers? We're now hiring (Remote – Europe): - Staff Frontend Engineer - Staff Backend Engineers - Support Engineer Join us 🚀 jobs.gem.com/polar

We've released the @trylatitude CLI tool. Easiest way to share and improve your prompts with the rest of your team. In beta, so expect some rough edges, but give it a spin!

@6a6763 Car parked successfully 86km away 😅

Anthropic talks about how to do multiagent: all the industry goes to multiagent right away Exact same thing happened when google started to talk about distributed systems, netflix with microservices and so on. Those companies are years ahead, have different challenges. It makes sense to understand what they do but the context is important (pun intended)

We're looking for Senior Software Engineers, ideally with a background in Ruby and React, to join this new team. We're starting from scratch, so you'd have a great impact from day one! 🏝️ 100% remote 🏥 Private health insurance 💸 60.5k€ and ESOP plan careers.factorialhr.com/job_posting/se…

@6a6763 Cutting edge EU DORA regulation

I’ve fixed orgs mid-crisis, rebuilt teams, and once traced a production bug to a submarine. Startups are weird — I get it. Need fast clarity? Book 15 min here: intro.co/IvanSuhinin

Only 3% of pets in Europe are insured. We’re here to push that number to 100%. @Barkibu isn’t just building a company. We’re building a category, with Dalma, Lassie & others who believe in adequate vet care for all pets. Thanks @stripe for helping us scale the mission

Some people might read this and think, that's just not my world, I am stuck in this world where software breaks all the time and everything I build is disposable. Even if that is kind of the case for you, there is still good news, because this isn't an all-or-nothing problem. It's a dial that can be turned; you can turn that dial in a direction that reduces flailing and results in more-stable long-term progress. You don't have to remove all the dependencies, because every dependency you remove contributes to stability. Even getting rid of 1/3 of your dependencies can do amazing things. You can look at all the things you depend on and divide them into two categories: major and minor. Major dependencies are things that, realistically, you are never going to have your own version of. I am never going to make my own graphics API, so those count as major dependencies for me (DirectX12, Vulkan, Metal, etc). I am not going to write my own CPU-side font rasterization, so anything I choose to use there (FreeType, stb_truetype) goes in that category. With Major Dependencies, you limit your contact surface with them: You call only the functions you really need, and you do this only from the surface of your program -- you don't build data structures deep into your program that propagate the particular data structures or API decisions of any of these systems. A good API author will help you do this (stb_truetype), a bad API author will be trying as hard as they can to screw you up and force you to become tied to their system forever (anything from Microsoft or Apple). Understanding that many API authors are hostile can cause a big change of perspective here, and once you see it, the correct tactics become much more obvious. So, that's the major dependencies. Minor dependencies are things that are smaller, and that you want to use much more thoroughly throughout your program: for systems programmers this might be a data structure like an expanding array or hash table, for Web, maybe there are some string or file operations that you like to do. Minor dependencies can be eliminated and it's not even hard. You just do one at a time: hey, I need this data structure, I have been importing this other code to provide that functionality, I have suffered X, Y and Z problems because of this, how about if I just implement my own simple version of this one thing? People can get scared of implementing core stuff like this, because they look at the implementation they are using now, and it looks huge and complicated and hard to reproduce. But the thing to realize is most of this implementation is spam. It is mostly doing things for people who are not you, for reasons you don't necessarily agree with, chosen by a decision-making method that is deeply flawed. Your own implementation can be cleaner and smaller, and it can give you good feelings when you go look at it. You don't need all the functionality of the thing you are importing; you only need 8% of the functionality. Implementing that is easy. Once you do this a few times, you have your own stable body of code that you bring with you from project to project. It won't break unless you mess with it. You can keep improving it if you want, incrementally over time, but the cost of this is small because this code represents stable algorithms that don't change with fashion, so work on this is never forced. Every big company has their own internal version of this, but the problem in that scenario is that a big company is full of people who want different things, and have varying levels of decision-making skill, so these usually end up not so good. But when it's your own personal thing, it can in fact be very good, and help make you happy on a daily basis. And, your software will break much less often. Which is great. @NotAShelf @ThePrimeagen x.com/Jonathan_Blow/…