• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

What do you do for work, anandtech offtopic folks?

Page 6 - Seeking answers? Join the AnandTech community: where nearly half-a-million members share solutions and discuss the latest tech.
Senior Planner for the County. Pretty fun doing land use and actually seeing your project being built out. Plus I get to work with our unincorporated communities on land use and how it pertains to healthy, sustainable communities. Because the County is ag-centric, we got a lot of run of the mill projects like large warehouse/storage buildings, but every once in a while we'll get a gem like an apartment complex or major subdivision. Then I can really sink my teeth into design of the buildings, landscaping and lot design.
 
Not everyone uses SharePoint. In fact, the majority don't.

So you’re an IT expert now? 85% of Fortune 500 companies use SharePoint in one form or another (SPO or on-perm). Businesses of all sizes are using it more and more everyday because of O365. In fact, SPO implementations were growing at a 70% rate and even on-prem was still growing at a rate around 25% IIRC. Additionally, anyone who uses OneDrive and Teams is also, in fact, using SharePoint since those products leverage it.

Any more statements you need me to correct? Not that your actual argument has any relevance to the discussion even if you were (and you weren’t) correct.
 
Speaking of Sharepoint, I can't believe how big it is. It's the worst CMS I've ever used.

As I said, it is jack of all trades but master of none. It generally suffers from poor implementation and training plans and as I said, most on-prem installs were horribly botched by people who didn’t understand enterprise architectures.

A couple years ago, a VP of a local consulting firm called me to ask for help on a horribly botched SharePoint install. The “consultant” these guys hired convinced them to drop from 8 web front ends down to a single web front end - for 600,000 users with peak load of 50,000 concurrent users. The “consultant” used a single account for everything, which is against even Microsoft’s most minimal guidance. And that isn’t even the worst thing I’ve seen. I think that’s another reason MS pushes SPO so hard - the on-perm product is a complex beast and they’ve given up after seeing the huge number of botched installs.

As a side note, the IT “Director” of the company who hired that idiot consultant and took his advice was eventually fired. So while the consultant was definitely a moron, the IT Director was an idiot for listening to such obviously bad advice.
 
So you’re an IT expert now? 85% of Fortune 500 companies use SharePoint in one form or another (SPO or on-perm). Businesses of all sizes are using it more and more everyday because of O365. In fact, SPO implementations were growing at a 70% rate and even on-prem was still growing at a rate around 25% IIRC. Additionally, anyone who uses OneDrive and Teams is also, in fact, using SharePoint since those products leverage it.

Any more statements you need me to correct? Not that your actual argument has any relevance to the discussion even if you were (and you weren’t) correct.
Yep we are using O365 in the school system now and it is obvious when using Teams, Notes etc. in the links if you watch what is going on that it is all Sharepoint based. and while I generally have no issue with MS stuff OneDrive for business drives me nuts. Since I am not on the back end I have no idea whether the issues we have with it are caused by the way we have implemented it or it is just a steaming pile of crap.
 
What's a better alternative?
Putting everything in an Excel document on a USB 1.0 thumbdrive in Fred's desk drawer: P

Sharepoint can be okay if it's done well, which it very rarely is. I know a couple of people who are huge Sharepoint fans and can actually make some decent use of it.
 
All our documentation is in spreadsheets and it's a pain in the ass. I ended up writing a basic CMS for all that stuff. Can search/add/edit entries much more easily now. I want to eventually incorporate a map so that when you search for a site it shows up on the map and you can see nearby sites too. Most sites have GPS coords so that should make it easier. Often times I need to know proximity to other sites so if a bunch of power outages come in I can confirm it's all the same area etc. Probably going to look into Openstreetmap and see how I can integrate it.

We have this espace thing (which I'm pretty sure is Sharepoint or some form of it) but it's cumbersome to use and hard to find anything, and it prompts for a password every chance it gets, super annoying.
 
All our documentation is in spreadsheets and it's a pain in the ass. I ended up writing a basic CMS for all that stuff. Can search/add/edit entries much more easily now. I want to eventually incorporate a map so that when you search for a site it shows up on the map and you can see nearby sites too. Most sites have GPS coords so that should make it easier. Often times I need to know proximity to other sites so if a bunch of power outages come in I can confirm it's all the same area etc. Probably going to look into Openstreetmap and see how I can integrate it.

We have this espace thing (which I'm pretty sure is Sharepoint or some form of it) but it's cumbersome to use and hard to find anything, and it prompts for a password every chance it gets, super annoying.


Or just have your gis people compute point to point road distance of all your sites, bracketing a max range and give you that. Then you can decide which ones to tuple for a crew.
 
I started writing an office wiki a couple years ago, but gave up on it. I only know half of what it takes to keep the business going, and no one else would have contributed, or even used it.

I spent a bunch of hours putting our job book into a spreadsheet so it's all searchable, and filterable, and only me and the engineer use it. The draftsman's a moron. Says he can't open my .ods file, and that's it. No curiosity. Didn't look, didn't ask, cause he's a fuckin' moron. Never clicked on the html document I exported either so it opens in a browser. I'm not telling him. I've spent waaay too much of my life making things easier for him, with no payback. The boss just asks me to fetch the data for him, or he uses his billing software.
 
Or just have your gis people compute point to point road distance of all your sites, bracketing a max range and give you that. Then you can decide which ones to tuple for a crew.

No idea what any of that means.

We're on our own when we want info, we dig it up in spread sheets we were given 20 years ago and do what we can with it. All I'm doing is making it easier to manage. It's not an official project so no outside help will be provided. Just doing it to make our job easier.
 
I try and figure out all the ways our contractors might try to kill our astronauts.

Well tell our shit government to give them a reasonable enough budget to hire important people directly instead of massive contractors for cheap dollars.

NASA is just one of many examples where the government is just too stupid to understand that the cheapest contract isn't the best contract - and just because the contract says "We will do X for Y dollars" - doesn't mean that is what will actually occur.
 
Back
Top