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.
515 karma · joined March 21, 2012
Proud Dad, Londoner.
https://www.moystard.com
[ my public key: https://keybase.io/moystard; my proof: https://keybase.io/moystard/sigs/LWyuLFYEKFo90vBjYIh9couQkb3-ZH0QCROfX-0Fqew ]
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.
Apply using the links below: Senior Data Engineer: https://jobs.lever.co/vestiairecollective/1cbe3026-88d4-42ef...
https://www.energate-messenger.com/news/239393/germany-becom...
Additional article highlighting the role of electricity exporter of France: https://www.bloomberg.com/news/articles/2023-08-07/france-is...
Living in SE London, I find already some planes incredibly noisy, so cannot imagine what it must have been.
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!
Engineering Manager (hands-on): https://grnh.se/3e676e461us
Senior Backend Engineer: https://grnh.se/87dcc97b1us
Backend Engineer: https://grnh.se/0b86dda91us
Senior Frontend Engineer: https://grnh.se/aa8093011us
Frontend Engineer: https://grnh.se/ba5bda281us
Senior iOS Engineer: https://grnh.se/23b59e4a1us
iOS Engineer: https://grnh.se/568c888a1us
Senior Android Engineer: https://grnh.se/7be58fae1us
Android Engineer: https://grnh.se/4c9848791us
QA & Automation Engineer: https://grnh.se/e819ee4f1us
About:
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.
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.
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.
Do you use excalidraw with a tablet or graphic tablet, or with your mouse? I have been exploring ways of taking manuscript notes.
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.
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
I really dislike this tendency of certain Javascript developers to qualify combining OOP with Javascript as "not understanding the language".
I had a decent experience with TypeORM after I spent time understanding how it works under the hood to optimise the queries (notably by defining the relationships better).
As you mentioned, the Node.js ecosystem is full of specialised libraries to achieve typical use cases such as authentication/authorisation, ORM/persistence, etc. The Nest.js documentation is a great reference as they include a list of recipes for all those common scenarios and how to implement them in a Nest.js backend.