Bubblehouse provides a white-glove, custom loyalty platform tailored for e-commerce brands — from small enthusiast shops to large enterprises (for example, we're powering loyalty for one of Mattel's brands). We're fast, lean, and love solving niche loyalty challenges.
We need a reliable Magento/PHP freelancer to tackle occasional Magento 2 tasks related to our Magento integration and problem solving for clients. You’ll be our go-to person for ongoing development and problem-solving related to our Magento integration module.
The ideal candidate:
- Has solid hands-on experience with Magento 2 internals (custom modules, observers, integrations).
- Writes clean, modern PHP, uses Composer & Git confidently.
- Knows how to diagnose tricky Magento issues.
- Can overlap partially with our team between 9 am – noon New York time for quick check-ins while actively engaged on our tasks.
- Can self-direct, communicate clearly, and invoice cleanly.
Work style:
- Fully remote, async-first. Occasional calls only as needed, we hate unnecessary calls.
I think your example is perfect. What he gave you is not a complete answer to why, because, as you say, he might have been doing a number of other jobs. So why roofs specifically? Add the description of how he inherited his father’s carpenter business but whenever he visited clients, they all had leaky roof, yadayada, and that he now feels happy enough to not look for any further changes, and you get the kind of answer OP is looking for.
Bubblehouse (bubblehouse.com) is a fast-growing custom and private loyalty platform for Shopify and beyond. Headquartered in NYC, the entire team is fully remote and spread across US and Europe.
We’re expanding our lean team of extremely experienced developers. Companies are switching from other platforms thanks to the customizations and flexibility that we offer, enabled by our pace and technical excellence, which we intend to keep for years to come.
Tech-wise, we’re running on Golang, and using custom data storage on top of local key-value stores, colocating the storage and compute on dedicated hardware servers, and reading data directly from mmap’ed pages of the database. Ever came across HN saying that one can run Twitter on a single machine these days? We’re doing that in production.
Zero lines of React, almost zero third-party dependencies (carefully vetted), every line of JavaScript manually written with respect and understanding of the web platform. We render HTML server-side like it’s 2005, and use Tailwind as a design language powering our custom theming engine.
We’re no enterprise company internally, but we power loyalty programs for large enterprises (as well as small enthusiast shops — this entire industry is woefully underserved).
We’re looking for:
1. Top to bottom understanding of the software stack, from the modern-ish web platform to CPU caches.
2. Thinking and problem solving outside the box. (We don’t _always_ go for unconventional solutions, but we do it often enough to require a person who can do justice considering the entire problem space at every step.)
3. Demonstrated ability and hunger to learn new things quickly. (Every month we’re doing things we have never done before.)
4. Broad experience across multiple programming paradigms, platforms and software stacks. (Not looking for someone who’s just a narrow expert.)
5. Demonstrated care for the software craftsmanship (which can take many forms, including side-, open-source or primary work projects, teaching, or simply playing with the latest tech).
6. Great spoken English (we value our communication beyond simple ability to convey crucial information).
7. Ability to communicate around 9am to noon time in New York time zone.
In return, we give you an environment where we solve very challenging problems with practical advanced technology in a lean and literally fast-paced environment (with features delivered in days) while successfully taking on entrenched market leaders and helping people across small and large businesses be more successful while pursuing their dreams.
Send your plain text cover letter to andrey+hiring@bubblehouse.com (our CTO will read & respond personally). Help us see how you stand out. Summarize your experience. Perhaps link to 1–5 impressive things you’ve built and proud of, link to where we can see some of your code (or attach some), include your portfolio/CV, describe the platforms and stacks you’re an expert in. How did you start programming? What are you most passionate about in technology? What are the most interesting or weird things you’ve done? What are your strongest held professional opinions? Please make your email easy to read, we’ll appreciate that.
Transmit is a file transfer app; it's used to get access to existing files on your own Google Drive without installing Google Drive's native app. Limiting it to a subfolder would defeat what I believe to be the most common use case.
It’d depend on what exactly you’re using it for - as an example, if you’re backing something up regularly that’d be fine.
The main thing I was thinking would be beneficial is getting user confirmation at better than the whole drive level. I think Google is trying to prevent cases where a third-party stores tokens on their servers which are breached, and in that kind of scenario it could be useful to push for scoping so e.g. if iA were breached the attacker could get your screenplay draft but not the folder where you backup your password manager or financial data.
Here’s practical experience from me running the tech side of a startup while sharing the author’s values.
Server-side rendering (the normal kind from 1990s):
1. It is glorious. Everything that 37signals has to say about it is true.
2. However. I really miss React-style components as an abstraction. There are many ways around it that we use depending on the case (plain CSS classes, our own tiny Go/HTML component library, HTML custom tags), but we’re yet to produce something as ergonomic for more complex compositions.
3. We’ve added Hotwired Turbo for smoother page updates. I find it’s a lot more orderly than htmx, but we do miss some things that htmx would offer.
CSS:
1. We started out with just plain CSS, using BEM and CUBE to structure it and manage complexity.
2. That still got us questioning the DIY nature of the U (utilities) part of CUBE — it got increasingly complex and random, and really just like every program grows a broken LISP interpreter inside, every custom CSS utilities library grows a broken copy of Tailwind inside. So we adopted the actual Tailwind for utilities. Tailwind is truly glorious, both for sheer productivity of writing the code, but also as a language for describing styling at just the right amount of detail — more powerful than CSS properties alone (hover:color-red-700, disabled:cursor-default), but more constrained than full CSS.
3. Tailwind introduces a build step, though, which sucks (and slows down the build by the whole second! My m2 Air can probably do a 60s supercomputer-level nuclear explosion simulation during that time.) Thankfully, part of our startup is doing custom themes for each client, for which actual Tailwind sucks even more (themes are edited at runtime, and you wouldn’t want to run actual Tailwind with its million Node dependencies on your server), so we’ve implemented a subset of Tailwind in Go, just the things we actually used, and it runs at runtime, eliminating any build steps for themes.
4. Bottom line: Tailwind is absolutely glorious as a shared design vocabulary. Non-tech people were able to adopt it and handle theming thanks to it. The actual implementation of Tailwind seems unacceptably slow, but I hear a Rust compiler is coming.
JavaScript:
1. Plain old JavaScript is great, but needs some structure. We found that structure in Hotwired Stimulus, which we absolutely love.
2. But again, I do feel the desire for React-style rendering occasionally. We embed our widgets on customers’ e-commerce sites, and a chunk of HTML rendered based purely on data coming from an API with live updates is a perfect case for React.
3. Needless to say, running code on other people’s e-commerce sites is where I would never dare use a React-based stack, because I’d spend the rest of my life doing due diligence on the dependencies. (Our competitors are much less responsible about this, and it works out for them too, so this is more of a principles thing.)
4. This is probably the case where an in-house 500-line implementation of React-style rendering would be preferable to anything else. We already have a 100-line version, but it lacks many desirable features.
Bottom line: Yes, you can (and should) run a modern startup based on a pragmatic server-side rendered stack, but you definitely want to add just a few modern things: something like Hotwired, something like Tailwind, some solution for more powerful components in your templates, and something like Preact for certain use cases.
A very under appreciated aspect of Telegram’s protocol is that it’s designed by very, very weird people. Telegram scooped up a lot of winners of ACM ICPC contests in Russia, some of whom I’ve personally met, and the design of the protocol is exactly in line with the code these people generally write.
It’s really a showcase of how very high IQ and outstanding mathematical abilities mix with a distrust of existing technologies and a lack of expert intuition coming from more normal industry experience.
Just try implementing MTProto, or at least read the low-level docs, and you’ll see for yourself. Crypto isn’t the weirdest part. The whole thing is an attempt to define a binary protocol in terms of grandiose mathematical concepts most of which didn’t even end up ever used in the actual protocol. And there’s zero thought given to what’s actually important, making a bullet-proof syncing between server and client states (and that results in numerous bugs to this day).
Can’t discount malice, but I don’t believe that’s the case.
When Telegram first launched this was exactly my hypothesis. They found some mathematicians and (to paraphrase Bruce Schneier) they immediately tried to re-invent cryptography -- badly. Which is fine.
I assumed that after a few years and some success, Telegram would get more serious about this and replace its crypto with something better (maybe Signal protocol) in the same way that WhatsApp did. I also thought they'd eventually back up their privacy claims by deploying default end-to-end encryption for non-broadcast chats. After all that's the trend everywhere: even Facebook Messenger is now encrypted! But Telegram never, ever did this. They kept on making loud claims to be a privacy-preserving messenger, but they never added real privacy.
Not necessarily. As long as some mashed pixels of the license plate remain, and assuming different license plates would result in differently mashed pixels, it might be possible to restore the original from the highly compressed image data.
From series of images, aka. video, sure. From a single image? Not so much.
In video there is a lot of temporal information and even if the spatial resolution wasn't high enough in a single image, one would be able to accumulate a higher resolution version of the scene using multiple observations.
Bubblehouse provides a white-glove, custom loyalty platform tailored for e-commerce brands — from small enthusiast shops to large enterprises (for example, we're powering loyalty for one of Mattel's brands). We're fast, lean, and love solving niche loyalty challenges.
We need a reliable Magento/PHP freelancer to tackle occasional Magento 2 tasks related to our Magento integration and problem solving for clients. You’ll be our go-to person for ongoing development and problem-solving related to our Magento integration module.
The ideal candidate:
- Has solid hands-on experience with Magento 2 internals (custom modules, observers, integrations).
- Writes clean, modern PHP, uses Composer & Git confidently.
- Knows how to diagnose tricky Magento issues.
- Can overlap partially with our team between 9 am – noon New York time for quick check-ins while actively engaged on our tasks.
- Can self-direct, communicate clearly, and invoice cleanly.
Work style:
- Fully remote, async-first. Occasional calls only as needed, we hate unnecessary calls.
- Compact, friendly, no-nonsense team.
- Quick task turnarounds, minimal bureaucracy.
Interested? Fill out this form to apply: https://bubblehouse.typeform.com/to/wsGgLyb2