Meta tags:
author=;
description= Artsy Mobile 2025 Wrapped ...;

Headings (most frequently used words):

the, artsy, of, using, engineering, blog, mobile, 2025, wrapped, two, years, next, js, at, retrospective, checklist, for, deploying, scary, change, typescript, magic, are, you, right, mongo, geospatial, query, parallelizing, jest, and, cypress, io, tests, on, circleci, hacking, around, safari, day, cookie, limit, third, time, charm, deprecating, kaws, stepping, out, knowledge, zone, context, to, simplify, very, large, react, form,

Text of the page (most frequently used words):
the (43), and (31), that (20), artsy (17), for (17), our (17), with (11), read (10), this (7), about (7), react (7), have (7), what (6), you (6), most (6), out (6), way (6), these (6), form (5), but (5), from (5), time (5), are (5), mobile (5), api (4), blog (4), years (4), many (4), more (4), #engineering (4), can (4), things (4), make (4), like (4), some (4), want (4), tests (4), they (4), one (4), string (4), been (4), via (3), artworks (3), only (3), not (3), use (3), using (3), its (3), into (3), after (3), experience (3), team (3), here (3), less (3), will (3), both (3), think (3), world (3), along (3), service (3), needed (3), when (3), share (3), cookie (3), safari (3), christopher (3), pappas (3), two (3), developer (3), app (3), los (3), angeles (3), type (3), welp (3), native (3), where (3), net (2), artsyopensource (2), careers (2), page (2), say (2), which (2), part (2), core (2), artwork (2), enough (2), context (2), first (2), was (2), ruby (2), later (2), process (2), through (2), before (2), landed (2), current (2), partner (2), very (2), post (2), short (2), who (2), name (2), kaja (2), engineer (2), also (2), change (2), all (2), love (2), thought (2), challenge (2), talk (2), down (2), functionality (2), decided (2), collections (2), kaws (2), works (2), wanted (2), several (2), how (2), system (2), roop (2), matt (2), dole (2), privacy (2), laws (2), their (2), often (2), around (2), apple (2), did (2), know (2), feature (2), user (2), came (2), recently (2), jest (2), parallelize (2), cypress (2), circleci (2), based (2), front (2), end (2), build (2), trying (2), take (2), get (2), complex (2), improvements (2), case (2), report (2), right (2), specific (2), strings (2), union (2), just (2), hello (2), typescript (2), palette (2), couple (2), changes (2), checklist (2), risk (2), exciting (2), your (2), involved (2), next (2), good (2), little (2), lets (2), success (2), engineers (2), begin (2), older, categories, archives, those, unfamiliar, fine, art, marketplace, knowing, follows, logically, partners, list, sale, integral, systems, known, whispered, halls, arty, new, york, headquarters, legendary, colossus, old, predate, v16, hooks, apis, entirely, version, built, 2014, haml, began, refactoring, jquery, full, having, expanded, considerably, original, implementation, least, gleaned, git, excavation, incremental, experimental, passed, hands, lap, laurabethdotdev, laura, bhayani, anna_carey, anna, carey, simplify, large, writing, introduction, berlin, entity, born, programmer, calling, myself, backend, may, emotional, identification, actually, see, background, university, graduated, philosophy, historical, linguistics, impractical, beautifully, theoretical, subjects, really, being, ideas, experiments, status, opposed, thinkable, alizenero, santro, stepping, knowledge, zone, let, why, learned, now, taken, folded, main, database, gravity, call, reasonable, collection, order, create, them, developed, called, named, artist, whose, put, realized, ago, able, group, bunch, together, happen, gift, guide, curated, antwaun, sargent, contemporary, prints, ifpda, fair, sprint, 2022, ceramics, lucio, fontana, tell, deprecate, something, mostly, worth, spending, effort, replacing, third, charm, deprecating, efforts, great, hand, rollout, creates, nightmare, users, without, extra, care, slightly, bad, approach, ccpa, gdpr, amongst, organizations, contend, consent, own, browser, retain, client, side, days, support, designed, protect, intelligent, tracking, prevention, itp, hacking, day, limit, regard, across, radar, sharding, free, integration, command, split, exploring, ways, improve, makeup, whether, implementing, express, integrating, rust, pipeline, always, reduce, amount, takes, code, cycle, place, exception, opens, ensure, timely, feedback, unit, pass, does, correctly, smoke, each, jobs, processes, said, tasks, devs, need, wait, scaled, whole, org, minor, radical, swc, compiler, hot, swapping, parallelizing, closed, turns, santa, monica, separate, neighboring, municipality, must, within, 25km, radius, default, sorts, queries, fielded, away, confirmed, asked, sure, gallery, didn, cut, shows, near, coordinates, got, galleries, area, weren, showing, exhibition, listings, mongo, geospatial, query, set, theory, bubbles, comment, says, even, though, fact, makes, because, tends, includes, const, check, node, web, repos, today, found, while, types, strict, design, pvinis, pavlos, vinieratos, magic, accidentally, taking, key, hours, better, pre, deploy, thinking, run, press, shiny, green, button, rolling, significant, breaking, production, environment, mission, critical, services, work, keep, eyes, posts, exact, project, coming, soon, definitely, caused, incidents, lately, getting, sketchy, stuff, talking, data, migrations, deploying, scary, crazy, well, bittersweet, tale, start, measure, could, agree, scratch, rebuild, internal, tools, rebuilds, fleeting, attest, there, extending, further, assign, task, platform, aren, too, familiar, modern, technology, then, succeeded, retrospective, would, made, might, applicable, past, year, has, apps, folio, started, finally, closer, high, performing, friendly, applications, enabling, rapid, iteration, superior, mounir, dhahri, 2025, wrapped, toggle, menu, open, source,

Text of the page (random words):
artsy engineering api careers artsyopensource artsy net open source artsy engineering blog toggle menu artsy mobile 2025 wrapped mounir dhahri the past year has been an exciting one for our mobile apps artsy folio and palette mobile and we started to finally get closer to where we want to be high performing and developer friendly react native applications enabling rapid feature iteration and a superior user experience we would like to share with you some of the improvements we made that might also be applicable to your react native app read on two years of next js at artsy a retrospective christopher pappas where to begin where to begin lets start with a good measure of success one that i think most engineers could agree on a from scratch rebuild of a complex internal tools app success with rebuilds is often fleeting as many can attest there s risk involved extending the challenge further lets assign most of the task to a team of platform engineers who aren t too familiar with modern front end technology and then say that we succeeded is artsy crazy or is next js along with our team just that good well it s a little of both and it s a little bittersweet in a way here s our tale read on the checklist for deploying a scary change matt dole lately i ve been getting involved with some sketchy stuff you know what i m talking about data migrations i ve been rolling out changes that have a significant risk of breaking our production environment for mission critical services it s been exciting work keep your eyes out for more posts on the exact project coming soon ️ but i ve definitely caused a couple incidents along the way after accidentally taking down a key service for a couple hours i decided i needed to have a better pre deploy process for these changes i did some thinking and came up with a short checklist to run through before i press the shiny green button read on typescript magic pavlos vinieratos pvinis at artsy we love typescript we use it in most of our node web mobile repos today i want to talk about a specific case we found while trying to make our types more strict on palette mobile which is our design system for react native check this out const welp hello world string welp is of type string like the comment says even though we have two specific strings the fact that we do a union with string makes welp have a type of just string this is because both hello and world are strings and the union tends to go to the type that includes the most think of set theory and bubbles read on are you using the right mongo geospatial query roop we recently got a report from one of our galleries in the los angeles area that they weren t showing up on our los angeles exhibition listings i fielded the report and right away confirmed when we asked our core api for shows near los angeles coordinates sure enough this gallery partner didn t make the cut turns out they are based in santa monica a separate and neighboring municipality they must not be within the 25km radius that we use by default for these sorts of queries case closed or so i thought read on parallelizing jest and cypress io tests on circleci christopher pappas at artsy exploring ways to improve the developer experience is part of our makeup whether it s implementing hot swapping for express js or integrating the rust based swc compiler into our front end build pipeline we re always trying to reduce the amount of time it takes for a code cycle to take place ci is no exception when a developer opens a pr we want to ensure they get timely feedback do their unit tests pass does the app build correctly and how about smoke tests each of these jobs are complex processes that take time and the more one can parallelize said tasks the less devs will need to wait scaled out to a whole engineering org minor improvements to ci can be radical in this regard two things came across our radar recently that we d like to share sharding via jest and a free way to parallelize cypress io integration tests via circleci s split command read on hacking around safari s 7 day cookie limit christopher pappas amongst the many many things that organizations have to contend with around cookie consent laws is apple s very own browser safari did you know that safari will only retain a client side cookie for 7 days this is in support of apple s intelligent tracking prevention itp feature designed to protect a user s privacy these privacy efforts are great but in hand with laws like gdpr and ccpa their rollout often creates a ux nightmare for users without some extra care here at artsy we ve landed on a way to make things slightly less bad and want to share our approach read on third time s the charm deprecating kaws matt dole roop how do you tell when it s time to deprecate a system if something mostly works ok is it worth spending time and effort replacing its functionality at artsy we realized several years ago that we needed to be able to group a bunch of artworks together if we wanted to have a page with all of the ceramics by lucio fontana or contemporary prints from the ifpda fair sprint 2022 or a gift guide curated by antwaun sargent we needed to have a way to make that happen we decided to call these things collections a reasonable name for a collection of artworks in order to create them we developed a service called kaws named after the artist whose works we wanted to put in several of these collections now 4 years later we ve taken down the service and folded its functionality into artsy s main database and api gravity let s talk about why and what we learned along the way read on stepping out of the knowledge zone kaja santro alizenero as i am writing my first blog post for artsy here is a short introduction on who i am my name is kaja and i am an engineer in our berlin entity as a ruby born programmer i am calling myself a backend engineer but that also may change and is more about emotional identification and less about what i actually do as you will see in this blog post my background is not in engineering at all in university i graduated in philosophy and historical linguistics both the most impractical but most beautifully theoretical subjects i can think of i really love being in the world of ideas and thought experiments that challenge the current status of what is as opposed to what is thinkable read on using context to simplify a very large react form anna carey anna_carey laura bhayani laurabethdotdev for those unfamiliar artsy is a fine art marketplace knowing that it follows logically to say that the form via which our partners list artworks for sale is an integral part of artsy s core systems this form known only as the artwork form is whispered about in the halls of arty s new york headquarters it is legendary it is a colossus it is old enough not only to predate react v16 8 hooks and context apis but artsy s use of react entirely the first version of the artwork form was built in 2014 using ruby and haml and began its refactoring into js jquery react a full 2 years later after having expanded considerably from the original implementation that process at least what we ve gleaned from our git excavation was incremental experimental and passed through many hands before it landed in the lap of the current partner experience px team read on blog archives categories page 1 of 28 older api careers artsyopensource artsy net