HN user
Opinions my own. Reach out through any of my public profiles. Employer = Google.
Website: https://go.mattj.io/hn
LinkedIn: https://go.mattj.io/linkedin
Twitter: https://go.mattj.io/twitter
Very cool! There are a ton of opportunities like this with SF systems!
For folks wondering about the public nature of this data: SFMTA separately publishes a full data set daily: https://data.sfgov.org/Transportation/SFMTA-Parking-Citation...
Note: depending on the language, you might have to do more work to ensure that the original data is in a format that base64 encoding will support.
For example, in JavaScript, that involves making sure it's a well-formed string. I did a write-up of that here: https://web.dev/articles/base64-encoding.
From the paper:
In this work, we present the first text-to-image diffusion model that generates an image on mobile devices in less than 2 seconds. To achieve this, we mainly focus on improving the slow inference speed of the UNet and reducing the number of necessary denoising steps.
As a layman, it's impressive and surprising that there's so much room for optimization here, given the number of hands on folks in the OSS space.
We propose a novel evolving training framework to obtain an efficient UNet that performs better than the original Stable Diffusion v1.52 while being significantly faster. We also introduce a data distillation pipeline to compress and accelerate the image decoder.
Pretty impressive.
Clear and legible pricing is essential. I took a look at the event page in question [1]. The "ea." seems like something that can be overlooked, especially given the comparatively miniscule font size (8px versus 14px for the price) [2].
On the checkout page, the fact that it is per ticket is clearer, but there's no total/subtotal information. Looking at the "Terms Of Use And Privacy Policy" [4], there's also this fun line:
You further understand and agree to pay service fees and delivery fees, which cover the costs of our operations, including the 100% buyer guarantee outlined below, the checkout security services, customer service, and the delivery of the tickets.
...and those fees are supposed to be shown during checkout. [5]
[1] https://www.ticketsales.com/james-taylor-tuesday-tickets-kou...
[2] https://i.imgur.com/raPeRac.png
[3] https://i.imgur.com/975Sp0a.png
[4] https://www.ticketsales.com/content/termsandprivacy.html
[5] https://help.ticketsales.com/support/solutions/articles/2600...
Hi there, thanks for the feedback! I overlooked testing with scrollbars set to always show, as Firefox recently started following macOS/Windows system settings rather than using its own setting. I've updated the CSS to use `100%` to rectify this. For this specific post, a bare link was also causing additional horizontal scroll, so I addressed both in https://github.com/devadvance/devadvance.github.io/commit/6a....
Thanks for posting this link. I saw this submission and remembered that Chromium had a terminal rendering mode, but couldn't manage to find this page, since I wasn't searching Ozone specifically.
The fork here goes even further, which is really cool.
Highly encourage exploring Flutter as well, at least for new platforms. Lottie animations would pair nicely, as would any future goal of expanding to web or desktop.
Highly encourage folks to take a look at Valetudo. I recently installed it on a Dreame Z10 Pro and it works well. Even without various integrations, I added a DNS record for it and can happily go to http://vacuum/ to control it locally.
For stainless, I've found it to be a combination of making sure there's enough heat before adding food, being OK with using a bit more fat (e.g., oil, butter) than I initially expect, using the right utensil while cooking, and deglazing as necessary.
You'd have to ask Broadsign for an official answer.
Educated guess: WPE WebKit only supports Linux [1] and Broadsign supports more than Linux [2].
[1] https://wpewebkit.org/about/faq.html#is-wpe-ported-to-non-li...
[2] https://docs.broadsign.com/broadsign-control/latest/broadsig...
I previously worked at Intersection, an out-of-home (OOH) advertising company. Intersection does digital screens (displays and kiosks) in addition to traditional formats.
This is all public information that was previously shared, so it may be out of date: the devices are Linux (Ubuntu) [1], running an advertising player (Broadsign) [2], which has Chromium Embedded (CEF) for web content [3]. The kiosk app was written in React [4]. It does things like load most data ahead of time to provide that "instant" feeling [5].
[1] https://ubuntu.com/blog/digital-signage-the-face-of-the-smar...
[2] https://broadsign.com/blog/intersection-selects-broadsign-na...
[3] https://docs.broadsign.com/broadsign-ayuda/configuring-splas...
[4] https://mattj.io/posts/2019-02-12-building-smart-city-kiosks...
[5] https://mattj.io/posts/2019-07-09-improving-perceived-interf...
Google Stadia | https://stadia.com/careers | Multiple locations (U.S., Canada, remote-eligible) | Multiple Roles | Full-time | ONSITE, REMOTE
Stadia is Google's cloud-based platform that lets you instantly play your favorite video games on the devices you already own. No more waiting for game downloads, updates, or installs. With Stadia, you have the freedom to decide how to play, what to play, and where to play across laptops, desktops, phones, tablets, and TVs. We're working to expand the availability and convenience of how people play the industry’s best games.
Through Immersive Stream for Games, we are also making our infrastructure and tools available to developers and publishers who want to build their own interactive streaming platforms, and deliver their games directly to their customers. We aim to grow the industry across gaming and other interactive streaming applications.
We're looking for folks for a variety of roles, such as software engineering, technical account management, technical writing, and more.
Some of our open roles include:
• Engineering Manager, Immersive Stream for Games, Stadia - https://careers.google.com/jobs/results/118099805332218566-e...
• Software Engineer III, Stadia - https://careers.google.com/jobs/results/108246707008873158-s...
• Staff Software Engineer, Technical Lead, Gaming Infrastructure, Stadia - https://careers.google.com/jobs/results/138082897664844486-s...
• Technical Account Manager, Stadia, Immersive Stream for Games - https://careers.google.com/jobs/results/121846987399013062-t...
• Technical Writer Manager, Stadia and Immersive Stream - https://careers.google.com/jobs/results/97960651848065734-te...
You can find more of our open roles here: https://stadia.com/careers
You can also learn more about some of our engineering work on our tech blog: https://stadia.dev/blog/
Questions? Reach out via LinkedIn or Twitter (check my bio).
Google Stadia | https://stadia.com/careers | Multiple locations (Canada, U.K., Germany, U.S., remote-eligible) | Multiple Roles | Full-time | ONSITE
Stadia is Google's cloud-based platform that lets you instantly play your favorite video games on the devices you already own. No more waiting for game downloads, updates, or installs. With Stadia, you have the freedom to decide how to play, what to play, and where to play across laptops, desktops, phones, tablets, and TVs. We're working to expand the availability and convenience of how people play the industry’s best games.
Through Immersive Stream for Games, we are also making our infrastructure and tools available to developers and publishers who want to build their own interactive streaming platforms, and deliver their games directly to their customers. We aim to grow the industry across gaming and other interactive streaming applications.
We're looking for folks for a variety of roles, such as software engineering, technical account management, technical writing, and more.
You can find our open roles here: https://stadia.com/careers
You can also learn more about some of our engineering work on our tech blog: https://stadia.dev/blog/
Google Stadia | https://stadia.dev/about/ | Multiple locations (Canada, U.K., Germany, U.S., remote-eligible) | Multiple Roles | Full-time | ONSITE
Stadia is Google's cloud-based platform that lets you instantly play your favorite video games on the devices you already own. No more waiting for game downloads, updates, or installs. With Stadia, you have the freedom to decide how to play, what to play, and where to play across laptops, desktops, phones, tablets, and TVs. We're working to expand the availability and convenience of how people play the industry’s best games.
Through Immersive Stream for Games, we are also making our infrastructure and tools available to developers and publishers who want to build their own interactive streaming platforms, and deliver their games directly to their customers. We aim to grow the industry across gaming and other interactive streaming applications.
We're looking for folks for a variety of roles, such as:
• Senior Developer Manager, Stadia Content Pipeline Lead - https://careers.google.com/jobs/results/115421438334116550-s...
• Technical Program Manager, Stadia - https://careers.google.com/jobs/results/126713413624570566-t...
• Software Development Manager, Stadia Porting - https://careers.google.com/jobs/results/141491078441116358-s...
• Engineering Manager, Engineering Productivity, Stadia - https://careers.google.com/jobs/results/128282199519568582-e...
• Senior Developer Manager, Gaming, Stadia - https://careers.google.com/jobs/results/79727291006886598-se...
• Program Manager, Stadia Payments Operations - https://careers.google.com/jobs/results/130720914531590854-p...
• Program Manager, Stadia Payments Operations - https://careers.google.com/jobs/results/102111673516466886-p...
You can find additional roles here: https://careers.google.com/jobs/results/?q=stadia
You can also learn more about some of our engineering work on our tech blog: https://stadia.dev/blog/
Maybe Chrome OS Flex will eventually support ARM Macs [0]? That would be cool for sure. I installed CloudReady for someone last year and it saved him from buying a new computer, and saved me from worrying about ongoing OS updates.
Disclosure: I work at Google and am speaking only for myself. I do not work on anything related to Chrome OS.
The fact that the post mentions hiring (cost) isn't my hesitation. It's that bringing cost into a conversation about the technical merits of a given technology can be a heavy-handed way of shutting down the conversation. In some cases, technical merits very much do justify the cost, but that can only happen by creating the space to find out.
Said differently: I believe it's often worthwhile to discuss the deeper technical merits of options without hastily jumping to a cost discussion.
My primary hesitation with posts like this is that it mixes engineering points (performance, developer experience, code sharing) with a more general business point: hiring.
Hiring is a cost. There are costs to any decision. Opportunity cost, risk, business continuity, operational costs, etc. Hiring is generalizable so it makes for an easy example here.
I would hope that experienced folks making decisions like "React Native or Flutter" would weigh the full gamut of costs in their specific business context.
Google Stadia | https://stadia.dev/about/ | Multiple locations (Canada, U.K., Germany, U.S., remote-eligible) | Multiple Roles | Full-time | ONSITE
Stadia is Google's cloud-based platform that lets you instantly play your favorite video games on the devices you already own. No more waiting for game downloads, updates, or installs. With Stadia, you have the freedom to decide how to play, what to play, and where to play across laptops, desktops, phones, tablets, and TVs.
We design, build, launch, and land the fundamentals that make it possible to include video game streaming in first- and third-party applications.
We're looking for folks for a variety of roles, such as:
• Software Engineer, Stadia Porting - https://careers.google.com/jobs/results/128018238983283398-s...
• Software Development Manager, Stadia Porting - https://careers.google.com/jobs/results/141491078441116358-s...
• Software Engineer, Graphics, Stadia - https://careers.google.com/jobs/results/79892054408078022-so...
• Senior Developer Manager, Gaming, Stadia - https://careers.google.com/jobs/results/79727291006886598-se...
• Staff Software Developer, Developer Services, Stadia - https://careers.google.com/jobs/results/124546505081004742-s...
• Engineering Manager, Engineering Productivity, Stadia - https://careers.google.com/jobs/results/128282199519568582-e...
• Technical Lead, Developer Tools, Stadia - https://careers.google.com/jobs/results/109913615693161158-t...
• Product Manager, Stadia - https://careers.google.com/jobs/results/111760946944189126-p...
You can find additional roles to apply to here: https://careers.google.com/jobs/results/?q=stadia
You can also learn more about some of our engineering work on our tech blog: https://stadia.dev/blog/
The article is hard to support or dispute when the contents are primarily anecdotal.
For example, it may be a more productive conversation once the 2022 point-in-time count of people experiencing homelessness is completed [1]. That will make comparisons to other points in time more effective.
Google Stadia | https://stadia.dev/about/ | Multiple locations (U.S., Canada, others) | Multiple Roles | Full-time | ONSITE
Stadia is Google's cloud-based platform that lets you instantly play your favorite video games on the devices you already own. No more waiting for game downloads, updates, or installs. With Stadia, you have the freedom to decide how to play, what to play, and where to play across laptops, desktops, phones, tablets, and TVs.
We design, build, launch, and land the fundamentals that make it possible to include video game streaming in first- and third-party applications.
We're looking for folks for a variety of roles, such as:
• Software Engineer, Graphics, Stadia - https://careers.google.com/jobs/results/79892054408078022-so...
• Software Development Manager, Engineering Productivity, Stadia - https://careers.google.com/jobs/results/119918908741165766-s...
• Product Manager, Stadia - https://careers.google.com/jobs/results/111760946944189126-p...
• Strategic Business Development Manager, Stadia - https://careers.google.com/jobs/results/79039168157491910-st...
• Product Lead, Infrastructure and Partner Experience, Stadia - https://careers.google.com/jobs/results/85154766151131846-pr...
And many more roles that you can find and apply to here: https://careers.google.com/jobs/results/?q=stadia
You can also learn more about some of our engineering work on our tech blog: https://stadia.dev/blog/
Generally this is an accurate take. I'd add two things:
...because they're realised they really have no idea of their exposure.
This is partially because it is often non-engineers being asked to figure this out. The "information security analysts" at F500s are asked to do a lot of unfair work, such as analyze risks related to decades-old software they didn't build.
...there's a whole business ecosystem in just being able to answer that question let alone do anything about security issues.
The first part (answering "what dependencies does my software have") isn't inherently bad. I'd emphasize the underinvestment in the second part more.
I'm perpetually impressed by the value FFmpeg adds to society. I imagine an accurate tally of all the places it's used would be impossible, but I can't help but imagine it would be eye-opening in it's breadth.
Two noteworthy items that stand out to me:
AV1 Low overhead bitstream format muxer
speex decoder
Congrats on the 5.0 milestone to all contributors!
Solid post and a well-done reflection on your experience. It's also great that you were able to not only able to ship something, but also get the experience of iterating on it and problem solving along the way. Definitely not an "intern project"!
Digging into a particular thread in your post:
Later I came to realize that they have a culture of building things inhouse and it shows.
[...]
The first I noticed was the old tech, as I mentioned before there is a lot of internally maintained technology and that's good for a few reasons like the fact that you're just a message away from contacting the world wide expert for the technology you're using. But it can also have it's downsides, you don't fully benefit from the fruits of Open Source and it could lead to stagnation and slow development.
You've shown some great observations about what might be simplified as "build versus buy", with buy having options like "actually buy" and "adopt FOSS".
As you grow in your career, I encourage you continue to dig even deeper into the ripple effects of this sort of tech decision. Yes, it might have been better tech than the alternatives at one point in time and there are internal experts for that tech one message away. Long term, that can become a form of institutional knowledge (risk) and sunk cost fallacy (we built it, we should continue investing in it).
In other words, remain curious and be willing to question decisions as the context, culture, and challenge evolve!
This is a really well-thought-out, nuanced take. I really appreciate mixture of "but there are still servers", not being able to stop a gold rush, and (refreshingly) the technical take on the implementation details.
It stands in such stark contrast to other content. For example, a web3 chat app announcement I saw yesterday [1]. I even joined the Discord to learn more and just found...hype.
I found this parenthetical to be amusing:
(visualizing this financial structure would resemble something similar to a pyramid shape)
Pyramid-shaped financial setups indeed :).
[1] https://twitter.com/MessagePartyApp/status/14791510011813765...
Overall solid introduction to the space. EDI was one of the things that boggled my mind early in my career.
What we’re seeing here is that while a standard can be opinionated about the structure of a document and the naming of fields, it cannot be opinionated about the contents of a business transaction – the contents of a business transaction are dictated by the idiosyncrasies of the business itself.
Maybe it's the engineer in me speaking, but this seems like a pretty unfortunate stance to take. Sort of similar to saying, "we have the concept of HTTP status codes, but we cannot possibly opine on the codes themselves."
A bit hyperbolic for sure, but not having opinions on critical multi-party information has led to things like the reluctance of financial services to support non-ASCII values for customer names.
Related to this valuation: it's a marketplace. Putting aside my thoughts on NFTs themselves, is there data that suggests the marketplace itself provides enough utility to justify the valuation?
Separately, I really do wonder if it's time that places like OpenSea borrow from traditional investment and provide some warning upfront.
For example, modified from the traditional investment verbiage:
Investments in NFTs: Not FDIC Insured • No Bank Guarantee • May Lose Value. Investing in NFTs involves risks, and there is always the potential of losing money when you invest in NFTs.
Throwaway phone numbers are either caught and banned by spam filters, or present untenable security-risks to the account.
It seems like you might have already found your answer: establish a full-fledged bifurcated online identity. Instead of throwaway, create a bona fide secondary/tertiary/etc. number, email, and so on.
The challenge is that the networks are using these identifiers as both connection points and implicit proof of identity/existence. Throwaway/anonymous doesn't work well for the latter use case.
Assume readers know the basics or will look them up [...] One of the beautiful things about reading on the internet is that google is just a click away.
Especially in the case of technical jargon, it's a good middle ground to link to a relevant definition directly. That avoids the friction of a suboptimal in-line definition and the friction of forcing a multi-click lookup. A beautiful part of the internet is links :).
Instead of leaving posts as a boring todo chore in the drafts folder, it's perfectly fine to just stop cold and publish if a wrap up doesn't flow naturally. Honestly, nobody cares.
While I agree with publishing incomplete content, I would argue that this is an exception to the "Don't caveat, just say it" section from earlier. It's often helpful to caveat incomplete content because it treats the reader with greater respect.
Putting aside gripping strength versus traditional wheels for a moment, it would be interesting to see if this would enable more efficient street geometries. For example, due to the reduced turning radius, could this open up additional safety buffer space for pedestrians at city crosswalks?
Excited to get to use this. One area of concern is i18n. The article touches on this briefly at the end, but I hope a zoned value can be used with Intl as well; having to use only Plain values would be frustrating.