Christian Kjær

1.6K posts

Christian Kjær

@codetalkio

Co-Founder/CTO at Yaay (https://t.co/1h6XFyTBlI) building the taste layer for the physical world 🌞 •• ✍️ at https://t.co/fOGJfINDR6 •• https://t.co/T286gLOCPe

Copenhagen, Denmark Katılım Ocak 2010

779 Takip Edilen230 Takipçiler

Sabitlenmiş Tweet

Christian Kjær@codetalkio·23 Tem

We’re looking for two people to join yaay to build the taste layer for the physical world - react native dev with solid experience (remote or on-site - fractional designer with flair for consumer (on-site) Read more and apply here yaaytravel.notion.site/Careers-Come-b…

English

234

Christian Kjær@codetalkio·1h

@joypbuilds @Apple "system data" is such a black hole - like, what do you mean I have +320gb of just some unknown data😭

English

joy p@joypbuilds·4h

there is no way apple still has no solution for cleaning out system data on your device without a hard format i have 180 gb of system data on my macbook too clutch up please @apple

English

961

Christian Kjær@codetalkio·7h

not gonna shame anyone, the provider we used has been super nice and I’m excited for what they’re cooking but it didn’t fit our way of thinking about data, and our unpredictable needs

English

Christian Kjær@codetalkio·7h

we’ve only ever had two outages at yaay, and both were from choosing a database that wasn’t fit for our purpose an important requirement: there must be a knob you can turn to pay more $$$ to handle more traffic we’re built for vitality, we need to control the ceiling ourselves

English

Christian Kjær@codetalkio·7h

@ipla03 is there a design decision behind this? I feel like with e.g. react-compiler you could now just generate a tag for each hook at transpile time and you’re no longer dependent on order I guess an original constraint was maybe that it should work raw in the browser

English

Fabrizio@ipla03·11h

That’s exactly why you can’t call hooks conditionally

BIKI ⚛️@biki__das

TIL: every useState in your component is a node in a linked list on the fiber. const [x, setX] = useState() → returns [hook.memoizedState, dispatch] React matches hooks by their position in that list (.next) Source: react-github.com/react/react/bl…

English

Christian Kjær@codetalkio·7h

@theo dev ergonomics matter apparently

Svenska

Christian Kjær@codetalkio·7h

@theo Xcode is probably the biggest thing keeping me from ever wanting to do Apps in Swift the dev experience is so horrible, and Swift ain’t gonna be the only language I’m using, so now I’m forced into at least two editors anyways

English

435

Theo - t3.gg@theo·15h

Xcode is legitimately one of the worst pieces of software ever made. Their entire platform is gimped by the worst developer tooling still distributed in the 2020's I cannot fathom how Apple stays ahead with such a blatant lack of care for developer tools

English

280

3.3K

251K

Christian Kjær@codetalkio·1d

@GergelyOrosz it’s a bit like getting handed a prototype that runs locally for one person and being asked to put that in production for all users there’s a canyon in complexity difference, and that’s not easy for non-technical ppl to see which leads to unrealistic expectations and burnout

English

Christian Kjær@codetalkio·1d

@GergelyOrosz AI has set insanely unrealistic expectations there has always been a subtle difference between a change/feature that takes days vs weeks AI has given ppl a tool for the former, so now they expect the latter to be just as easy, but it just isn’t

English

253

Gergely Orosz@GergelyOrosz·1d

Can confirm this is a global trend based on so many additional messages+comments. It is hitting eng leaders far more. Product leaders also. Ofc outside of Eng leadership burnout/uncertanity feels higher than before but this group feels it so much more. Will write about it

Gergely Orosz@GergelyOrosz

Interesting trend: CTO/ Head of Eng / VPE folks at startups and mid-sized companies are... leaving / burning out. Hiring for these roles is HARD, but even after filling the role, they will often leave a few months later and take a career break And they have v good reasons

English

597

89.2K

Christian Kjær@codetalkio·1d

apparently our account got archived as inactive 😅 dunno what kind of activity was expected for an alerting software other than..sending alerts?

English

Christian Kjær@codetalkio·2d

no notice or anything, found out by trying to log into our account and it said welcome as if I was a completely new user hope they can restore everything, but not confidence inspiring for the software which literal job is to ping me when something is wrong

English

Christian Kjær@codetalkio·2d

okay, crazy coincidence: the day we have an outage is the day incident.io just decided to wipe/reset our account? only found out when I was checking to see if we had a gap in our alerting only to find out that everything had fired but nothing had paged me

English

142

Christian Kjær@codetalkio·3d

@posthog feel free to steal ideas! 😄 a “prompt LLM” step would be fantastic in workflows, especially if it can have MCP context Right now we’re using the API call block to call our own systems that are already hooked up (e.g. for the triage, but also for translation of tickets)

English

Christian Kjær@codetalkio·3d

to be honest, a better approach than replacing is to use AI to build powerful integration layers ontop for example, we’re combining PostHog support + workflows to integrate App Store Reviews, AI triage and investigation pulling prod data, and integrating it into our App

Gergely Orosz@GergelyOrosz

And this is exactly why “SaaS replaced by AI coded software” is not viable for any company that has a an ACTUAL business. It’s a fun exercise to rebuild ticketing/o11y/feature flags etc… but do you really want to maintain it? Do you want updates, oncall etc to be YOUR problem??

English

242

Christian Kjær@codetalkio·3d

the AI investigation is honestly insanely helpful: it’ll figure out what the user was doing around the time they wrote the ticket, that relates to the ticket, and has access to error logging and prod logs as well to immediately see if it can find a root cause

English

Christian Kjær@codetalkio·3d

we let PostHog be the engine for that - I don’t wanna waste time building interfaces, managing auth, etc and we use AI to create all the various integration points it’s just about thinking smart: maintenance is the worst burden to take on - reduce it if you can!

English

Christian Kjær@codetalkio·3d

a third one: we vendored expo-maps in order to fully integrate it with our App’s flow, adding clustering support in native code, moving things to background threads, and tailoring it to our customization needs

English

Christian Kjær@codetalkio·3d

another example is porting the GraphQL deduplicator project, which is fairly small and contained, from JS to Rust so we could integrate it into our Rust GraphQL API to reduce the amount of data sent over-the-wire

English

Christian Kjær@codetalkio·3d

bun’s rewrite to rust is probably the project that inspired me most in how to approach using LLMs for development i’m much more aggressive porting/rewriting code, or vendoring dependencies to tailor them specifically to our needs in ways that doesn’t make sense to upstream

English

114

Christian Kjær@codetalkio·4d

@angerman it doesn’t have vision understanding? That’d kinda make it useless for any meaningful frontend or mobile work - that shit never render like you wish it would from code alone

English

moritz ✨@angerman·4d

GLM's lack of eyes is really handicapping it right now hard for me. Sigh.

English

147

Keşfet

@joypbuilds @Apple @ipla03 @theo @GergelyOrosz @posthog @elonmusk @BarackObama