Midnite is a next-generation betting platform that is built for today’s fandom.
We are a collective of engineers and designers who all share a passion for building the best sportsbook & casino experience possible.
Midnite | Senior Backend Engineer | Remote (UK Only) | Full - Time
Midnite is a next-generation betting platform that is built for today’s fandom. We are a collective of engineers and designers who all share a passion for sports and gaming. We exist to bring fans closer to the games they love through the rush of winning money.
We're searching for a skilled senior backend engineer to play a pivotal role in shaping Midnite's technological foundation. You’ll be responsible for constructing APIs for our mobile and web applications, producing robust and maintainable code within specified timelines.
Our tech stack is primarily implemented in Python and hosted on AWS, incorporating technologies such as Flask, Pytest, Mypy, Docker, PostgreSQL, SQS, S3 and Terraform, and we deploy daily. While familiarity with these technologies is preferred, it's not mandatory; what matters most to us is your commitment to maintaining high engineering standards
I'v gone from home assistant to smart things to openhab and its been stable and simple to set & forget.
It's great to setup via the UI, easy to backup and restore as once you actually start to build it into the foundations of your house you start to value the stability of it
I still never used OpenHab (at the moment running HA but not happy about it).
I’ve tried developing custom components for HA and it was so bad, there’s no docs at all and Python being untyped language doesn’t help either. Just out of curiousity I’ve googled OpenHab docs to understand if I could achieve similar there and their docs are awesome, full and well written. (and it’s Java so half of the code IntelliJ will write for you)
For reference, the IEEE 802.15.4 spec is ~800 pages long. 900 pages does sound like a lot considering that Matter (AFAIK?) doesn't directly spec any hardware or transport details - those being covered in 802.15.4 and Thread.
Granted, we should remember that those 900 pages include base details that, probably, CSA are not planning to change in the foreseeable future. They need to be very thorough.
To answer your real question: device manufacturers will likely use the Matter SDK. It would be a huge undertaking for a smart-light manufacturer to re-write all of that code from scratch!
I haven’t read the spec, but I believe that some backwards compatibility is built in, and there’s a degree of complexity involved in making a robust framework that isn’t general purpose (like Wifi), but instead offers compartmentalisation of different device types and use cases.
I agree with the manufacturer concerns, but many were in a bit of limbo while Matter and Thread languished in draft RFC hell. The spec was always ‘coming by the end of the year’, and obviously impacted by the pandemic.
At least now, there is some certainty and a path forward.
Is matter actually an open standard? When I last looked into the CSA stuff you had to pay a few thousand dollars a year to become a member to access any specifications
My understanding is that the standard will be open when it's final, but the working draft is not. The reference implementation is open during development: https://github.com/project-chip/connectedhomeip
Disclaimer: not speaking for my employer or CSA/Matter (I have done paid work on the reference implementation).
Setting aside the radio incompatibilities, various web articles says Matter was Zigbee Alliance "Project CHIP" and later rebranded to "Matter". And "CSA Connectivity Standards Alliance" is itself a rebranding of "Zigbee Alliance".
If the pdf reference docs are not relevant, I guess I don't understand why they're hosted at the domain "csa-iot.org".
As I understand it, Matter uses Thread to communicate with low power devices.
Thread uses the IEEE 802.15.4 PHY and MAC.
Zigbee also uses the IEEE 802.15.4 PHY and MAC, using the same frequency bands as Thread as far as I understand it.
Maybe a new radio is needed if you want BLE commissioning (is this required?), but for operation any chip with a IEEE 802.15.4 PHY should support both Thread and Zigbee.
I think it can run on wifi or Thread (possibly zigbee too if I’m reading the wiki right) but I may be wrong. It also uses BLE but I think only for initial setup.
Our customers use our world-class sports, esports, and game wagering platform to interact with the games they care about.
Fresh off the back of our series A, we are looking for roles across the whole engineering skillset & experience levels.
Our tech stack is implemented in Python, is hosted on AWS and includes Flask, Socket.IO, PostgreSQL, Redis, Elasticsearch, SQS. All our code is linted, tested and automatically deployed to our test environment.
Strongly disagree and I've noticed this is a common trait amongst developers. I think it stems from the fact they are more comfortable on the CLI and are used to poor interfaces that they more easily justify a sub-par UX. Just look at how many HN "readers" are out there because this site subscribes to the same philosophy
Mild disagree. Emoji aren't that bad, and certainly have their uses; however, most of the time they look dramatically different than the surrounding text, and can be quite distracting. If they're trying to communicate something important, that works fine, but often the important stuff is buried in the text, and the emoji simply hurt the readability.
Also, there's an issue sometimes whereby people who have nothing worthwhile to say thing that adding a few emoji will now make their message worthwhile...
I would love to see some real sale stats if those claims are real? I have no idea how much they are supposidly outselling zigbee or z-wave devices.
From a purley anecdotal standpoint, you start with the wifi devices as they are low barrier to entry, (no hub required and normally comes with some sketchy 3rd part app); If you decide to go all in and buy more than a handful you naturally progress towards the zigbee/z-wave devices and ether a fully managed Proprietary "do it for me" system like SmartThings, or you go down the self managed route with HomeAssistant or OpenHAB.
Ditto, but with z-wave devices instead. What makes you think CHIP is the next standard thats up for mass adoption when there is a bunch of competition in this space, with the likes of Sidewalk from Amazon or Thread which I think is what Apple are rolling out to the homekit enabled devices?
Amazon and Apple are both members of the CHIP working group. As far as I know, CHIP uses Thread as one of it's protocols (the other being a BLE derivative). Sidewalk uses WiFi, which is not very efficient for low-powered devices (eg. sensors, switch etc.)
Well to be honest, I really like the open-source approach that they have decided on for the development of the standard. You can follow the development of it's reference implementation on the Github repo of the project: https://github.com/project-chip/connectedhomeip
Midnite is a next-generation betting platform that is built for today’s fandom. We are a collective of engineers and designers who all share a passion for building the best sportsbook & casino experience possible.
We are hiring across multiple roles:
- Backend Engineer - https://apply.workable.com/midnite/j/FFAA2713D3/
- Junior Backend Engineer - https://apply.workable.com/midnite/j/CC0C6DF5C6/
- iOS Engineer - https://apply.workable.com/midnite/j/834FBB445D/
- Junior iOS Engineer - https://apply.workable.com/midnite/j/0ECC18C9A8/
Please mention hacker news in your cover letter!