The Lounge is rated PG. If you're about to post something you wouldn't want your
kid sister to read then don't post it. No flame wars, no abusive conduct, no programming
questions and please don't post ads.
What really annoys is that it didn't tell me it was going to do all this: I ran One Note, and it said "log in to Microsoft ID". So I did, and suddenly it thinks both PC's are the same. Which is fun, because this keyboard is UK, and that one is US ...
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
I use a large cursor/mouse pointer on the machine hooked up to my 4K monitor - I do want most things to be kept in sync, but the large cursor on my other machines with "regular" monitors looks ridiculous...
One of our clients I work for decided to go for proprietary CMS and get rid of the bespoke CMS solution that worked from last 5 years. But they are now struggling as for each small custom change, the company is asking for money and lot of money. Our existing system also talks to various 3rd party API's and also our apps talks to our API etc. So all this communication needs to be moved over to new proprietary CMS solution. This again will cost them bomb.
Now in order to save them some money, I am wondering if somehow we get the users data of the proprietary CMS API on a regular basis (If it can be done on real time, it will be even better) and update our DB. If we can do this autonomously, we will not have to move all other 3rd party integration to this new proprietary CMS solution.
Note: I am assuming, that this new CMS API will provide access to the user data which we can export or can autonomously upload to our db.
It would be good to know your views on this situation. Has anyone of you experienced something similar and does it makes sense or even possible to get the user data in real time.
This won't help you much. I'd love to know how they (your client) decided to go down this path without apparently considering all of the consequences. Surely your access to your client's user data which is now in the hands of a third party (ha ha) depends entirely on the deal you are able to cut with this third party. The fact that the client has allowed their own data to be locked up in this way seems almost bizarre - perhaps I am misunderstanding something.
"The whole problem with the world is that fools and fanatics are always so certain of themselves, and wiser people so full of doubts." - Bertrand Russell
You don't expect customers to consider the consequences!It's your job to consider the consequences and tell them why their crazy idea won't work.It's their job to ignore you and do it anyway, and then blame you when it doesn't work
This is exactly what happened. Obviously, they haven't reached the blaming stage yet. Few key employees left the company due to this decision.
I'd love to know how they (your client) decided to go down this path without apparently considering all of the consequences.
They were looking for a quick win solution and obviously ignored what technical guys suggested i.e. to go open source CMS route rather than proprietary solution. Few left the company due to this decision. They were just looking at the outer picture.
There are loads of mature, well-supported CMS's available (as they have been for years). Many are extensible or open source too.
When they've finished writing their own CMS, I'd suggest they move onto writing their own ORM and then their own programming language.. why stop at a CMS?
[Spoiler: It'll all end badly (and expensively) and they'll choose an off-the-shelf CMS]
Ah, I see you have the machine that goes ping. This is my favorite. You see we lease it back from the company we sold it to and that way it comes under the monthly current budget and not the capital account.
Sounds like they chose the wrong CMS. If customisation is a priority they should have gone with one that supports your own custom modules\plug-ins etc so that the in-house devs can take care of that rather than paying the CMS company to do these things.