This is a neat idea (and good looking product), but unfortunately the issue is the people who tend to interrupt you in the office ignore all explicit signals in my experience. Wearing noise cancelling headphones is an accepted sign of “in the flow, pls don’t interrupt” yet some folks feel like it doesn’t apply to them. Or they’d just stand next to your desk waiting for your attention. I’m pretty jaded (and probably s…
> Wearing noise cancelling headphones is an accepted sign of “in the flow, pls don’t interrupt” Well, someone could always say, sorry I thought those were just regular headphones. :) Anyway, my philosophy is that I'm being paid by my employer not only to do work, but to help others do their job as well. I WANT to be the person that my co-workers are comfortable walking up to and asking questions even if I am in the m…
Busy Status Bar
501–510 of 546 posts
Re: Busy Status Bar
#502Earlier quoted context omitted.
> Eventually people will realize the light is busy when the person isn’t really busy Like the geniuses that block off their whole day everyday on their calendar or set their Teams status to unavailable all day.
> the geniuses that block off their whole day everyday on their calendar as someone who leaves themselves open to hear out others with their "hey do you have a second to check this out" ideas y'all are missing out
Re: Busy Status Bar
#503Earlier quoted context omitted.
Put a CO2 + temp/humidity sensor in there and it's a no-brainer. The sensors could be nice to hack on too.
And double the price? Temp/humidity is simple enough, but reasonably priced CO2 sensors with any accuracy are an issue
Re: Busy Status Bar
#504Earlier quoted context omitted.
Reductio ad absurdum: If its for recording studios, fine. If not, get off my lawn, its just reinventing having a conversation. It's telling that both obstinate refusals to not understand what its for end up on unrelated stories about bosses. Let's call it PHB derangement syndrome. It never seemed likely it was that confusing, it's pretty hard to have been alive from 2020-2024 and claim that there's never any reason f…
I might be doing the famous "just use ftp" to dropbox. But I highly doubt it for this product.
No one's trying to lay claim to if this individual product "becomes Dropbox", and you're not saying you can build it in a weekend, which is the comment you're referring to.
I think you may be swapping in a bailey of "oh we're arguing about whether this will be "successful"" because the motte of "what is this for, it can't work!?" was obviously stupid, as you've ceded.
Re: Busy Status Bar
#505Re: Busy Status Bar
#506Earlier quoted context omitted.
Or the person is always busy, and to contact them a person should use slack, email or some other method.
And then they don't respond to email or slack. Are they missing it? Ignoring it? No one knows. Meanwhile, time sensitive deadlines come and go. There's no clear, easy protocol that works for everyone, unfortunately. Some people are always going to operate on the 'better to ask forgiveness than permission' model. And I say this as someone who is often in the 'always busy' camp.
Most employees probably have enough credibility to explain away one or two missed deadlines, but not 5 or 6 in a row without providing actual proof.
Re: Busy Status Bar
#507Earlier quoted context omitted.
No one who is in engineering would say something like this. I can only conclude your job is auxiliary to engineering. In which case: I don't think someone who isn't an engineer should be talking about what is and isn't possible with respect to how engineers work. It's also a good idea that when engineers do tell you how they work -- not to ignore everything they say. Since Afterall -- you're not actually the one doin…
I am a software engineer and most of them I have met throughout my career do not work on tasks that require 24/7 silence. Basic communication is important for every task and if you cant handle that you are simply not suited for the job.
Urgent message! It's time to complete your annual anti-bribery training refresher.
Urgent message! It's World Mental Health Day, and we're rolling out a new employee health and wellbeing policy.
Urgent message! Don't click 'yes' if you're offered an OS upgrade, crowdstrike doesn't support the new version.
Urgent message! All employees are required to complete mandatory training on chair usage. Click here to get started now!
Urgent message! The production website is down, please join the conference call we'd like to ask you about query explain plans.
Urgent message! Would you recognise a phishing attempt? Take 5 minutes to run through this refresher training and keep our corporate data secure.
Urgent message! The lyon office squash club is looking for new members.
A professional needs a strategy to stay productive despite the noise, while not missing the occasional needles in the message haystack.
Re: Busy Status Bar
#508If you're looking for something with an addressable LED matrix in a clock style form factor, the Ulanzi TC001 [0] for ~$50 is worth having a look at. Doesn't quite have the same aesthetic but inside it's just an ESP32 (flashed via the USB-C port) and there's various mature open source firmware replacements. I use awtrix[1] on mine and it's very easy to tie in HomeAssistant for doorbell notifications and that sort of…
Re: Busy Status Bar
#509Looks like lametric alternative?
Re: Busy Status Bar
#510Earlier quoted context omitted.
Perhaps the real solution is to default to "busy" and only show "available" on a trigger, like web-browsing or staring into space.
Nobody will mark oneself as not busy, either because the management might be taking note or one truly doesn't make time to be open to more work. It looks like to me that due to previous solutions, people try to improve upon in the same domain. May be the premise of the solution is wrong.
However, one does not always plan in advance to get into deep focus, so I don't really believe this problem is solveable in a useful way. Basically, we need to learn to regain focus quickly and push people away when busy.
Also, async interrupt methods are great when used properly: don't you hate it when someone pings you with "hi" or "hi, I have a question" or similar and waits for your response? Good practice is to ask a full question which allows the other side to respond when they can without interrupting.