Just wow. You have to take into account the year these were made and its zeitgeist... It took a different mind to come up with those back then ... nice ... well done ... thats the importance of artists .... they are the ice breakers .. the rest just follows ...
> Would the CEO resigning or getting laid off, make your situation any better if you were one of those laid off?
No, of course not. But he is the leader, and he guided the company to a point where certain areas became "over-invested or under-performing." In other words, he didn’t do a good job. So, it should be him stepping down. Nobody ever said being a CEO would be easy.
>and he guided the company to a point where certain areas became "over-invested or under-performing."
And now he's fixing it by cutting those under-performing areas.
>So, it should be him stepping down.
Why? How would that help the company get better? Do you think competent CEOs are like cogs that you can pick a new one from the stack of LinkedIn applications whenever the old one makes a mistake, and then slot him in the existing machine and everything will magically work better?
>Nobody ever said being a CEO would be easy.
Exactly. That's why you don't rush to replace the devil you know with the devil you don't.
Why don't you start your own company so you can be a model angelic CEO then? Why bother working for these "evil" guys? Or work for a local mom and pop shop instead of a publicly traded company?
I ran a business which is why I know how hard it is and why I prefer working for someone else and accepting the trade-offs. You're the delusional one here wanting to have your cake and eat it too.
It comes down to genuine, natural unforced interest (its there or not) and mastering the ability to systematically deal with and how to tackle the next unknown. After years this make you a true wizard.
Agreed. I ran a log ingestion infra 8 years ago doing 20k msg/s sustained on RabbitMQ ... back then we went through a lot of instabilities though they settled over time with new releases. Great times. Besides a quality product the development/release process was very professional and mature.
The biggest issue back then was finding a quality client implementation for the language you were using. Not sure what the status of that is these days.
AMQP and MQTT are both industry standard protocols. Also, RabbitMQ allows you to abuse the limits set by these standards.
Its unfortunate your team ran into performance issues, as Erlang can be inefficient in some situations. Were you using static routes on the DNS load balanced parallel consumers, or relying on the disk caching mechanisms?
They don't but they do if you have too much of them. In my experience, the amount of meetings only increased when working remotely. I would welcome a meeting budget ... how many time one is allowed to spend in meetings over a certain time window ... once consumed you cannot be invited to, organize or join a meeting anymore.
Informal "meetings" became impossible and got replaced by formalized meetings. What could be resolved with a quick look over the table to the two other devs I need to talk with, and everyone else on the team was nearby and could hear or join the discussion, now must be a formal calendar invite because otherwise we built an information silo.
I had an example of that just this Friday (but really every day). A peer review got so complex that chat wasn't nearly enough, the PR comments were getting repetitive, and it resulted into 3 full draining hours of calls full of misunderstanding, stuck shared screens, "please can you zoom your editor I have a much smaller screen than you", etc. We used to solve issues like that with a quick look on the display next to us, maybe 20 minutes of on and off discussion while doing other things, few more quick looks and it was done. Same team, same people, less senior than now (before covid).
I love the flexibility but hate everything else about remote work.
I am cofounder of Jamscape, a startup that is trying to replace as many video meetings as possible with short ad-hoc face-to-face conversations that you can then share with others, and with actual eye contact. Perhaps a tool like this could help cut your meeting load.
you used more words but it sounds like your product is a video meeting product. I'm not sure having more meetings with your product will cut down on the number of meetings I have, but I understand why you would rather I have meetings on your platform
sure, but if it's meaningfully better then people should know about it and try it out and decide for themselves. I don't care that Google wants me to use their product because it makes them money. I search there because it's better than the alternatives I've tried. If this meeting product is better then by all means, let's hear about how it's actually better rather than dismissing the product owner for wanting you to use their product because it makes them money.
we're all well aware of how zoom/meet/teams meetings suck by this point. a product that manages to make them less onerous so I'm less exhausted at the end of a day off then would be a godsend.
Thanks! Jamscape is free to download and use, at https://jamscape.com. Currently only for macOS & Windows, but we are working on broader platform support. Very happy to help you test if it is something for you and collect your feedback.
It uses real time face recognition to give a very accurate presence indicator, so you never risk calling people when they’re not actually in front of the camera, it crops your face tightly with AI so you don’t have worry about what you are wearing or your surroundings before accepting or making a call, and it uses an AI video codec that boost eye contact and facial expressions even over low bandwidth and long haul connections. When the call is over it creates a transcript that is easy to share with others, and that others can use as a base for follow up calls or discussions, thus reducing the need for everybody to be in every call to stay on the same page.
It has a do not disturb mode and an async “ping” mechanism that protects your focus time while still allowing others to indicate that they would to talk when ever it is convenient.
I actually assumed it would have a DND mode, as that's a standard part of other software in this genre. However, at least in my experience, do not disturb modes don't really resolve the issue unless it's acceptable to just keep it in that mode all the time. I don't know in advance when I will be in a state where disruptions will be problematic, so I can't plan ahead. And when in a flow state, I certainly don't have the level of external awareness required to know that I should enable DND.
This sort of thing is still an issue in-person, of course, but in-person has the advantage that when you're in person, you can tell at a glance if someone shouldn't be disturbed. That mitigates the issue a little bit.
It is a tough problem, really, and I doubt there's a technological solution to it.
And that's not even getting into the issue that such a system means you can't ignore the fact that you're constantly under surveillance. If I can't ignore that, then being under constant surveillance has really terrible effects on my mood and ability to concentrate.
There may be no technical limitation to not setting dnd all the time but it effectively means you either have this app for some reason other than the main pitch or you're forced under this apps surveillance/interruption mode by the org. In either case the thing solved in this scenario is not reducing meeting interruptions for the user.
I think I lean with the others that the problem this app aims to solve is not really a technical problem. That said it doesn't mean there won't be lots of businesses interested in the app.
In the workplace, being DND all the time is not a thing that can realistically be done. It's not socially acceptable and I'm quite sure that your boss will sooner or later demand that you stop doing it.
It is optional and not on by default. If not it falls back to mouse and keyboard activity tracking. The advantage of using the camera is that it works even if you are not touching the computer, like when reading or watching YouTube, using another device, etc.
That is actually not the feedback we are getting. And as I said the way it is configured by default does not divulge and more information than e.g. the green dot in Slack or Teams, the rest is up to you.
What feedback are you getting? The implication is that you have users that are constantly surveilled by video and input device monitoring, and that they are telling you they are enthused.
The users we talk with are tired of meeting overload and some also feel lonely working remotely. They appreciate that we are trying to cut down the time they have to spend in meetings, and that a Virtual HQ tool like Jamscape make them feel more like a part of a team, as in the good old days where everyone were in the office together. Some dislike having the camera on all the time, both because of privacy concerns and for practical reasons such as this conflicting with other apps (this is only a problem on Windows, macOS allows the camera to be shared by multiple applications), but after we added the option of using keyboard/mouse event monitoring* instead nobody has complained about feeling surveilled.
We are developers building a tool that addressed the problems with remote working we have experienced ourselves (I have personally worked remotely since 2011), and we are not trying to build a surveillance tool, as none of us like to feel surveilled. We have tried to make everything tit-for-tat, so that you only get out as much information as you yourself is willing to give. For instance, you can show live video of your face, and if you do that will be able to see live video of others, but if you turn off your own video you also lose the ability to see others.
*) this monitoring, as provided by the underlying OS, does not let us see individual keyboard events, only a monotonically increasing events counter, so there are hardly any privacy implications.
I have no experience with this particular implementation but I do have experience with some important business process developed in Azure Logic Apps, which is kind of the same in spirit I believe.
From what I have seen, these kind of frameworks facilitates the worst possible combination of factors: A solution designed, created and implemented by non-programmers, not using a programming language ending up in a production environment.
One could argue this is a success in its own but I have only seen these kind of things hit their limits almost immediately after the initial POC and evolve into terrible tech debt. Just learn to program or script already.
That being said, I do not want to disrespect the effort into building this and perhaps there is a place for these kind of solutions I yet have to experience.
Fair enough I'd say :) The concern is understandable, but I honestly think Pipes is different.
The operations Pipes can do are at the same time very generic and very targeted. It's stuff like "Download this url" and "Filter this feed for that word", and it gives you a selection of blocks like extract and insert with which you can manipulate the data in the pipe (or the feed, depending how you look at it) a bit more freely. There is surprisingly a lot that can be done with that, especially with a replace block that supports regex, but it's not a deep abstraction layer above things that are not mappable to rather small operations.
That would be a win, but then the hideous code becomes the spec, and it becomes a project ten times the size to reverse engineer the "spec" into an actual spec.
