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.
Same old, same old. In an interconnected grid, everyone is importing and exporting from and to everyone. Germany (which you are referring to), is still an exporter of electricity.
Only until something brings down the French grid. Power generation should not be too centralised since that creates too many opportunities for failure, accidental (storm, fire) or intentional (sabotage, war).
it was landing, so it wasn't much noisier than say a 747, but a bit noisier. or perhaps i was just used to it - my dad was an RAF vulcan captain (same olympus engines as concorde, minus reheat) and if you had a squadron of them taking off on QRA you learned the real meaning of noise!
We used to live under the flightpath for the departures from Heathrow to the US, not far from Reading. The evening flights would go over, which you could feel in your body, then moments later catch the light of the setting sun as they headed west. It was quite inspiring.
The Vulcan is (or was!) my favourite plane sound, beating out the Merlin-engined stuff and even Concorde. Four Olympus engines, plus the howl. Can't be bettered! https://www.youtube.com/watch?v=H_ARSE8jEHQ
glad you enjoyed the howl, but, sorry, it didn't have afterburner (reheat). i still probably prefer merlins - the BoB flight Lancaster flies over me here in Lincoln occasionally. and also the Red Arrows!
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.
Another one: they conflate Type and (Locator) Instance in a unique way that just about nothing else in TS does. Those are two very different things with the same name with Typescript's (antiquated) enums.
There are too many ways to accidentally import/redeclare/rescope the Type of an enum so that TS "knows" the Type, but because that type (generally) has the same "name" as the most likely (Locator) Instance it assumes the same access applies leaving runtime errors behind when that Instance isn't actually imported/available. Typescript has no easy way to tell the difference between access to the Type isn't access to the (Locator) Instance (nor vice versa). Reasoning about those runtime errors or preventing them is additionally tough for people too because of the same "name" problem for two different things.
This is something that's painfully hard to avoid in cases where you are trying to encapsulate an API's Types separate from its imports/exports because they might be introduced or manipulated at runtime (plugins, sandboxes, proxies, etc). Unfortunately, this is also too easy to accidentally do even when you aren't intentionally doing something complicated like that (trying to generate automated .d.ts files in a bundling toolchain, for example, when APIs are in the boundary space between unintentional public API and internal tree-shaking or optimized symbol renaming).
Let's turn it around, union types are so much easier to use and so much more powerful. Enums have only a small subset of the features, are not compatible to JavaScript code and are hard to understand (read the docs about type script enums and you will see).
To be clear, this kind of structure is only emitted for numeric enums. String enums with explicitly declared static values are roughly equivalent to the equivalent Record<string, string> (runtime) and a corresponding type T[keyof T] (type check time).
IME, most of the complaints about enums apply only to numeric ones.
The major exception to that AFAIK is the fact that enum members of any type are treated as nominally typed (as in A.Foo is not assignable to B.Foo even if they resolve to the same static value). I am among the minority who consider this a good thing, but I recognize that it violates expectations and so I understand why my position isn’t widely shared.
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.
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...