crtlaltdel

I never cared for the software, but I’m excited to see how the direct listing plays out.

yup, read them many-many years ago. i spent a large portion of my youth immersed in this world (figuratively, literally) :)

I echo folks in this thread who suggest being honest. In my opinion it says a lot about you and how you communicate, as well as a lot about how the org thinks about their employees. i mean, you essentially took a sabbatical (regardless of the reasons) after more than 5 years in your career. individuals may quibble about the length-before-break, but several companies have a sabbatical-like perk built into their comp plan.

^this. i recently had to explain this to a product manager who wanted the user's email and password to be autofilled it they landed at the login page.

id argue that “psychedelic engineering” has long been a goal of researchers.

oh, and in pretty sure i’ve heard tell of “psychonauts” before...

yeah this sounds more like it would be a T&C clause

^couldnt agree more. both packaging and presentation of the subscription tiers being simplified would help imo. that said, certainly a/b test that!

^this, to me is hard to imagine. i’ve taken it for granted that i didnt need to track the lengths of my list-like data structures myself. at the least checking the length of the list of dictionary keys via some builtin.

absolutely. not just onboarding, but in-app help/references. it is dispiriting to get kicked out to some faq site.

same here

linux has become quite common in iot, which has really expanded what a lot of people consider an “embedded system”. we built a platform on a custom BSP for OpenWRT for industrial applications where an rtos or plc wasn’t needed.

this is inspiring, i cannot believe i had not considered this before!

1997, pwd for the charter school dialup account was stored WarGames style. i used to connect after midnight until about 4am a few days a week. lasted until they switched providers.

If you've designed the wiring correctly this can be done at the central junction, isolating the that room (or rooms). then, when you setup that sound system in the room you already have the speakers built in. just plug into the port on the wall :D I've seen this kind of setup several times, though it was the early 2000's, before the massive proliferation of wifi audio.

note: one of the reasons i saw a lot of this was the company i worked for acquired a structured wiring company (system in a box) that did lots of home/office AV work

how large is the team, if i may ask?

this is a very good point, and i have had the same experience. its also super common for very cheap, very low end custom ics to use i2c for the same reason; keeping the pin count and package size down

i think only half of this would be shiny ;)

I think this is a solid assessment and a great data point for founders assessing their idea.

to be clear, after we saw that we were all positive that Blade Runner was going to happen before we graduated middleschool...

a couple of years prior to that era i worked for a Giant Electronics manufacturer who used WD desktop class drives in RAID and CCTV/DVR systems. we had insane corruption issues, burnout issues and so on with a large number of our devices. at the time i was running an rma shift for the product line so this was notable to me. we also had devices come in with Seagate drives, but they had been in operation much longer before they showed any issue and were from a few previous model releases. at some point the drives were "value engineered" and WD was selected. in the end they had to suck it up and put in a server class drive (something with a high duty cycle rating). once they did the fails slowed dramatically. when we went over the data it looked like all most of the failing devices were installed in 24/7 video monitoring applications, and several were installed in poorly (or not at all) ventilated spaces. after a while we put temperature tags on the inside of the chassis to get a sense of the max environmental temp (yeah, didn't work if it had been on a truck for week in transit, but at least a field tech could check).

if i had to guess, i'd say that the digital signage company was "value engineering" the system components ;) i was in industrial controls and never had a sense that the signage folks were laughing on the way to the bank...

i distinctly remember this product, not because i used one...but because my friends and i learned about it on compuserve! same night was my first use of mosaic. prior all my “internet” use was actually either muds via telnet or dialin bbs.

one could a/b test the plan label and put some teeth behind the many useful assertions in this thread, if one were so inclined

yeah, differential data lines; common in serial applications where you want to protect from noise. a lot of the higher level dialects are built off something like (if not the) rs485 electrical layer.

yeah, i have seen properly shielded cat5 ethernet based implementations in similar environments. i would have to say that i've seen far more industrial / heavy-commercial applications that used cat5 because "thats whats on the truck" that have had to be re-pulled. in a lot of instances things would "work" for a bit, until the operating environment changed (plant was expanded, circuits re-wired, etc). one of my favorite instances was an electrical submetering system where all the meters would go down at the same time every night. it started happening after the system had been active for a few months. the culprit turned out to be a cell modem the system owner had added. the modem had been mounted inside the NEMA enclosure that housed a datalogger. the datalogger would query values from the submeters over a serial bus (rs485) every minute, aggregate it and upload it to "the cloud"...once a day. the cabling the electricians had used was some generic roll of cat5. it wasn't shielded (and thus the shield wasnt grounded). the modem would broadcast, and that event would "crash" the serial bus, cutting off communication with the submeters. we (not really "me", but the EE i sent to the site) removed the modem relocated it outside of the enclosure so the system could operate while the correct cable was pulled. we had built a number of systems with integrated modems (we had SKUs with that configuration), so the issue really was the wrong cable for the application being used because it was common and on hand (and cheap; legit industrial serial cable can cost you upwards of $1/foot).

honestly, this feels like a great feature for today, especially with the prevalence of smartphones and the mobile web! now we have devices that are mostly easier to type/compose messages on and the fierce rush to build an app for everything has imo reduced the "cool factor" of a bespoke native app. i hate installing a new app to use a service if the app is buggy and the workflow could be done some other way (even responsive webapp). personally, i really enjoy sms based UX.

tbh i got it on a whim, thinking that i'd revive my love of writing fiction, stage plays and poetry. sort of a "recapture the heady days of my youth" thing lol. since then i've found that any editor with a minimal interface and markdown support makes me feel better about writing, in general.

Yes.

It was used as an industrial communications bus to coordinate slave devices from a master controller. Drop-length was a non-issue as the majority of our devices used an in-rail (DIN mounted) interconnect bus. The larger "drops" were often a under 10" and just jumped one DIN rail to the next DIN rail in the cabinet.

This was selected for the following reasons:

1. These devices were installed in HEAVY EM environments (think in close proximity to very large electric motors) and the electrical characteristics

2. The system topology physically supported multi-drop

3. We had a good deal of talent with CAN experience

4. Our device was already supporting a bunch of wired and wireless protocols (rs422, rs485, ethernet, btle, wifi, etc) and tbh CAN support was a gimme on the SOM we used as the device's core, so initially it made it into consideration by chance

i've never used bear.app, but i do a lot of writing in Ulysses[0] and selectively copy/paste back into Notes if needed.

[0]: https://ulysses.app

i know it signals the end of something people poured their hearts into...but i do enjoy reading these kinds of announcements. i find it fascinating to see how founders communicate to their communities and now-ex-staff. in a lot of cases, i find it inspiring.

yeah i think of it more as multi tenet safety