The premium experience does have a heavy price tag attached to it since they repeatedly increased the pricing. In the UK, the first plan is now £7.99 / month.
This eventually led me away from Dropbox and I am now an iCloud user - the convenience and cheap prices eventually convinced me, even though I wish a Linux client existed.
Hello from Vestiaire Collective, the leading global marketplace for second-hand luxury fashion. As a B-Corp, we are working to build a more sustainable future for the fashion industry.
We’re expanding our team in the Seller Experience Collective! We're looking for a Senior Data Engineer and a Senior Frontend Engineer based in London.
Join us to solve fascinating engineering challenges and help build a sustainable tomorrow.
After trying many hardware and software solutions for easily switching between my rigs, I settled on something much simpler: a monitor with a KVM built-in. It does not have to cost you an absolute fortune. I personally chose the Gigabyte 34" M34WQ; it's probably one of the very best purchases I made in the past two years, and it simplified moving between my work and personal rigs an absolute breeze.
Vestiaire Collective | London, United Kingdom | Full Time | Hybrid (3 days / week on average in office) | Engineering Managers & Software Engineers | https://www.vestiariecollective.com |
Looking to work alongside a talented product & engineering team on a truly global and high growth platform?
The Seller Experience team, based in London, is expanding and we are looking for Engineering Managers, Software Engineers and a Product Owner to help us build a best-in-class user experience for our sellers and depositor.
Join us to contribute to the transformation of the fashion industry towards a greener future!
The leading global online marketplace for desirable pre-loved fashion. Certified B Corporation.
Our mission is to transform the fashion industry for a more sustainable future by empowering our community to promote circular fashion.
Our platform is unique thanks to our 23 million highly engaged buyers and sellers, and rare inventory of 5 million items including 20,000 daily new-ins.
Vestiaire was founded in 2009 and is headquartered in Paris with offices in Tourcoing, London, Berlin, New York, Hong Kong, Singapore, Lisbon, Seoul.
Writing is undervalued by a lot of software engineers. It is the best medium for sharing information, live (thanks to collaborative documents), but also over time (documentation). An essential skill to develop.
I do believe however that fewer and fewer engineers will actually take time to develop that skill and will rely on ChatGPT and co in the future to generate most of the written content based on draft notes.
I usually use the unknown type and leverage type guards for isolating the exact type and processing it. If it falls down the type guards, process as generic error.
Interested in having the quote as well, and ideally the presentation/keynote/interview that came with it.
From my experience, breaking down a monolith without first identifying and isolating its bounded contexts (as in DDD) is a recipe for disaster. With your domains completely entangled in a single codebase, you won't pull only what you want and you will have to bring a lot of undesired code, behaviours and side effects with it.
The safest recipe, in my opinion, is to break down your monolith in bounded contexts (or ideally, to have focused on it from the start), so you can better reason and understand the advantages and trade-offs of moving each specific domain and responsibilities out of your unique codebase.
I saw often teams being motivated in moving their code out of a legacy codebase because of the huge technical debt, but they were bound to suffer a death of a thousand cuts by just bring the same debt in a new service, and adding network constraints on top.
My experience is very similar to yours, and I concur with your conclusion. After 5 years of React, I joined a new organisation as engineering lead, and the team had embraced Angular before I joined.
Coming from the React/Next.js world, I was really puzzled with that decision as I still had in mind the trauma of the Angular.js -> Angular migration and the breath of fresh air that React had represented at the time.
As most engineers out there, I had an urge to stick to what I knew would work, but I resisted that urge and gave Angular a chance. I do not regret it; Angular and the structure the framework provides is a game changer for a large project; the conventions make the code and the architecture predictable/testable/scalable. Our time is spent on delivering value for our users. This is, in my opinion, the best quality a technology can have when working on a fairly large project.
Sideloading is not accessible to everyone, even though it's fairly easy to achieve. Most users, even technical, would not want to rely on such methods for installing a development environment (or customising their devices for example); Any tentative for monetising an application that depends on sideloading would be bound to fail at scale.
Is the context I described responsible for the lack of market? It may be.
I still think that iOS is the best mobile experience out there, but it's
Proud Dad, Londoner.
https://www.moystard.com
[ my public key: https://keybase.io/moystard; my proof: https://keybase.io/moystard/sigs/LWyuLFYEKFo90vBjYIh9couQkb3-ZH0QCROfX-0Fqew ]