Re:New York City bans TikTok for government employees
by madrox on Wednesday August 16, 2023 @07:11PM
(#37155104)
If this isn't a government or a bank then run like hell because that company is ripe for being disrupted.
Re:New York City bans TikTok for government employees
by martin_a on Wednesday August 16, 2023 @07:55PM
(#37155455)
Nah, it's just that our company is part of a larger group (2k+ employees in Europe), so the IT tends to focus on the other companies more. Also my whole e-commerce stuff is very unique to us which reduces reusability for anything they set up for me. From there on it's just a short way to "this will only help him, that will help dozens of people" and your projects get pushed another quarter...
To be fair: Most of the people don't really need much more than SAP, Excel and Word and that's... "uncomplicated" to run with some proxy and firewall config etc.
Re:New York City bans TikTok for government employees
by madrox on Thursday August 17, 2023 @07:43PM
(#37169803)
I don't think anything you said alters my point, but I wish you luck. That's an awful environment.
Re:New York City bans TikTok for government employees
by 1lint on Thursday August 17, 2023 @01:59AM
(#37157796)
I recall someone in a similar situation who was able to convince IT to whitelist a cloud VM for testing website deployments. In addition to the website, this VM also hosted a wireguard server running on ports that happen to be commonly used for databases.
I need to do development regularly for our workflow systems. That includes a NodeJS based process, so npm has to work, I backup code to gitlab, need to use Postman/Insomnia to test APIs, whatever.
I don't have admin rights on my windows machine, because that's obviously unsafe. All the software on my machines is outdated, as I need to open a ticket for each and every update of VS Code and whatever I'm using and answering those tickets can take some time. Also I feel dumb doing that.
After "securing" the systems even more, IT changed the proxy server. npm didn't work from one day to another. They had to debug it for a week and finally gave up and just whitelisted it and whatnot. Will probably only survive until the next update.
gitlab doesn't work anymore, as basic auth is not supported by the proxy server anymore. I don't have the time (nor the rights - ha!) to fiddle around with that all day to get it working, so there's no versioning happening and "backups" or collaboration are based on local file systems or sending mails with the code attached, too.
My local environment of our workflow server can't connect to the app store to update the integrated apps. Something with the proxy, I don't know. So I'm developing against outdated versions of everything...
Want to connect to external APIs? Need to create a ticket so something besides Outlook and the browsers can connect to the outside world. Sometimes it doesn't work, so... you guessed it... make a firewall/proxy exception. Just takes a day or two.
Also updates in core infrastructure like proxy and firewall are not communicated. So you come into the office monday morning and everything is burning and nothing works anymore. "Yeah, we changed the proxy on Saturday..." Fuck it.
Final thing: One of my biggest projects is to provide a public API to create an easier onboarding experience and one standardized way to place orders with us... IT wanted to do it with their software partner, no other ways possible. We already had something ready we could have bought, deployed and customized in 3 weeks time. Now it's half a year later and the test version is ready. Endpoint URL looks like hell and _every single user_ needs to have his IP whitelisted to connect to the API. Even for the testing endpoints. For security reasons obviously. I'm just done with it.
edit: Yeah, slightly off-topic but had to vent somewhere. Thanks for your patience.