com. example.com. subdomain.example.com.
512 karma · joined April 21, 2011
com. example.com. subdomain.example.com.
The trouble is exclusively with old customers that don't use the Saas, don't want to use it, and still run the software on their own server. They believe they bought the software and therefore own it. Paying again for something you own is, understandably, not something people gladly do. But then again, software isn't a thing, it's a work in progress. A concept hard to grasp for some people.
On the other and, that exact same customer already ordered and paid for updates. That's one of the reasons I'm annoyed to have had that update discussion.
It's an online appointment scheduling software, btw.
And to me it looked pretty spot on. I imagine it's pretty hard to find the exact same position after twenty years.
> I remember a person from the old West Germany saying to me that they'd like that wall back twice as high and the same depth underground because of all reunification cost and the entitled attitude of 'osties'
That sounds like a very selfish person. Freedom for our east german brothers and sisters, unless I have to contribute...
From my experience if you are a small company and fix a reported bug in a timely manner, nothing bad will happen. As long as your customers see that you're reacting quickly, everything is going to be fine.
What interests me more is whether the broad user base cares enough to change their habits. Does it become freaky enough for them that they'll change the way the use the platform? (Doesn't matter if it's Facebook or any other website.)
That being said, I do finish side projects from time to time, mostly because I can still see the potential after working on it for a couple of ours.
I'm sure it's hard on all the AV vendors out there but with Microsoft Essentials and Windows Defender I don't see the need for a third party AV.
1. First engineer is motivated an has great qualitative and quantitative output.
2. First engineer's opinion is being ignored when second engineer is being hired. Can't be good for motivation.
3. First engineer has to fix the work of second engineer. Qualitative and quantitative output suffers. Motivation of the first engineer decreases further.
4. Warnings to the management are being ignored. First engineer gets so frustrated that he quits.
5. Second Engineer has now free reign. Even if quantitative output is still the same, the quality totally tanks.
I don't recommend that the first engineer quits because that would be a pretty big decision to make without trying to fix the situation first. But if management makes such a severe error in this early stage of the startup, there may be some more "interesting times" ahead.
I've come to the point where I'm glad that interviewers show their cards this way. If a company does stupid things like this, I really don't want work for them anyway.
I know there are times when you can't be picky and have to be glad to get a job but I don't believe for a moment that the work environment will turn out to be great after they pull stuff like that in the interview.