Pre-Planning new domain and environment
-
@gjacobse said in Pre-Planning new domain and environment:
@scottalanmiller said in Pre-Planning new domain and environment:
@gjacobse said in Pre-Planning new domain and environment:
It’s the business - designs will be large file- GB each. It’s also the requirement of the owner.
So it's a hobby, not a business. Businesses have one requirement: profits. Hobbies have requirements "as designated by the owner that don't reflect profits."
No - not a hobby, there will be about a 100 initial employees.
Can't have it both ways. Either he's mandating that he's a hobby, or he isn't. Number of employees is completely irrelevant. You stated that "business" was off the table. Is that not correct?
-
@gjacobse said in Pre-Planning new domain and environment:
Some specifics I still cannot discus - and since there isn’t a contract - no point.
Then there is really no way to be planning. Not in the slightest. Everything has a place, but almost everything you are mentioning are the "niche cases" where you'd need some serious justification for even talking about - unless it's a hobby and it's all to make someone feel like they have what appears to be a legacy business, instead of an actual one.
-
@gjacobse said in Pre-Planning new domain and environment:
But, there is a heavy requirement for anti-intrusion (nothing to do with domains i know), and heavy security and limitations... serious “principal of least privilege”
All reasons to rule out domains. Why mention this in the context of justifying a seemingly odd decisions, only to reinforce how odd it is?
-
@scottalanmiller said in Pre-Planning new domain and environment:
@gjacobse said in Pre-Planning new domain and environment:
@scottalanmiller said in Pre-Planning new domain and environment:
@gjacobse said in Pre-Planning new domain and environment:
It’s the business - designs will be large file- GB each. It’s also the requirement of the owner.
So it's a hobby, not a business. Businesses have one requirement: profits. Hobbies have requirements "as designated by the owner that don't reflect profits."
No - not a hobby, there will be about a 100 initial employees.
Can't have it both ways. Either he's mandating that he's a hobby, or he isn't. Number of employees is completely irrelevant. You stated that "business" was off the table. Is that not correct?
When / where did I say it was a hobby?
-
@gjacobse said in Pre-Planning new domain and environment:
@scottalanmiller said in Pre-Planning new domain and environment:
@gjacobse said in Pre-Planning new domain and environment:
@scottalanmiller said in Pre-Planning new domain and environment:
@gjacobse said in Pre-Planning new domain and environment:
It’s the business - designs will be large file- GB each. It’s also the requirement of the owner.
So it's a hobby, not a business. Businesses have one requirement: profits. Hobbies have requirements "as designated by the owner that don't reflect profits."
No - not a hobby, there will be about a 100 initial employees.
Can't have it both ways. Either he's mandating that he's a hobby, or he isn't. Number of employees is completely irrelevant. You stated that "business" was off the table. Is that not correct?
When / where did I say it was a hobby?
"It’s also the requirement of the owner."
When you said that the owner was not considering the business needs but setting requirements. Clear as can be. It's a requirement. A requirement that isn't "do what's best for profits" means that he's overriding fiduciary needs and determining non-business goals are taking precedent. Ergo, a hobby.
YOU didn't say it was a hobby, you repeated to us that he told you it was a hobby. The implication being that he was informing you, and then you us, that we are to take off our business/IT hats and put on our hobby hats, which is fine, because we need to know if the goal is good IT, or making an owner happy for needs only he can define.
https://mangolassi.it/topic/22351/defining-the-hobby-business-vs-a-true-business
-
Okay- by your definition in the thread-
Is this for a hobby or true business that makes profit on a product sold to corporation or retail
This is very much a for profit business. And therefore - by your definition a true business
-
@gjacobse said in Pre-Planning new domain and environment:
@scottalanmiller said in Pre-Planning new domain and environment:
@gjacobse said in Pre-Planning new domain and environment:
It’s the business - designs will be large file- GB each. It’s also the requirement of the owner.
So it's a hobby, not a business. Businesses have one requirement: profits. Hobbies have requirements "as designated by the owner that don't reflect profits."
No - not a hobby, there will be about a 100 initial employees.
Remember - Scott calls 95% of all businesses hobbies... soooooo...
-
@gjacobse said in Pre-Planning new domain and environment:
Okay- by your definition in the thread-
Is this for a hobby or true business that makes profit on a product sold to corporation or retail
This is very much a for profit business. And therefore - by your definition a true business
That's not actually what that thread says.
-
@Dashrender said in Pre-Planning new domain and environment:
@gjacobse said in Pre-Planning new domain and environment:
@scottalanmiller said in Pre-Planning new domain and environment:
@gjacobse said in Pre-Planning new domain and environment:
It’s the business - designs will be large file- GB each. It’s also the requirement of the owner.
So it's a hobby, not a business. Businesses have one requirement: profits. Hobbies have requirements "as designated by the owner that don't reflect profits."
No - not a hobby, there will be about a 100 initial employees.
Remember - Scott calls 95% of all businesses hobbies... soooooo...
Because they are. Because they don't act as businesses and don't function to make profit.
-
@scottalanmiller said in Pre-Planning new domain and environment:
@Dashrender said in Pre-Planning new domain and environment:
@gjacobse said in Pre-Planning new domain and environment:
@scottalanmiller said in Pre-Planning new domain and environment:
@gjacobse said in Pre-Planning new domain and environment:
It’s the business - designs will be large file- GB each. It’s also the requirement of the owner.
So it's a hobby, not a business. Businesses have one requirement: profits. Hobbies have requirements "as designated by the owner that don't reflect profits."
No - not a hobby, there will be about a 100 initial employees.
Remember - Scott calls 95% of all businesses hobbies... soooooo...
Because they are. Because they don't act as businesses and don't function to make profit.
Oh, I didn't disagree...
-
@gjacobse said in Pre-Planning new domain and environment:
Okay- by your definition in the thread-
Is this for a hobby or true business that makes profit on a product sold to corporation or retail
This is very much a for profit business. And therefore - by your definition a true business
That's absolutely missing the point and totally misstating what I said. "Making profits" is not the same as "profits as the primary goal." He's been clear with you, and you with us, that profits aren't the final deciding factor. That he hopes for profits too is not in question. Nor is that it is a hobby.
MY definition of business is that profits are the goal, not an artefact.
-
If it is like most hobby businesses, you can never tell the owner that that's how it is perceived, because they won't like it. Most hobby businesses have a goal of "feeling like a business", often because it seems cool or looks good to family, friends, or people you meet at the bar. In order to serve the "hobby", it has to convince people it isn't a hobby or the purpose has been defeated. So you'll rarely be able to actually talk honestly with the owner about it, and you'll always be stuck using "goal discussions" and working from things like "requirements" rather than "profits." If profits were the goal, additional requirements wouldn't really be needed.
But once you know you are working with a "requirements" owner, you know it's a hobby and you know that he knows its a hobby. But we all lie to ourselves, it's part of the human experience. So while he knows, he's also trying to convince himself it isn't true, almost always. It's just how these things work.
But while you can't have that frank conversation with him, you have to be honest with yourself or you're IT journey is going to be fraught with danger as you can't do honest, good IT without upsetting him and you can't make him happy if you do purely good IT.
-
I may understand what you are referencing. However- since I can’t say much about the company until a public announcement is made - and there will be one - maybe.
I haven’t had the chance to speak with him and my proposed department head - so,..there that.
I respect the owners stance, but wont have that information until then... and from that stand point, not important right now.
But - I have every intention to do right by Enterprise IT standards.
-
Multi Gigibyte files we have had a devil of a time with Onedrive/Sharepoint and multi-gig AutoCAD files and ended up moving back on prem for them.
-
@jt1001001 said in Pre-Planning new domain and environment:
Multi Gigibyte files we have had a devil of a time with Onedrive/Sharepoint and multi-gig AutoCAD files and ended up moving back on prem for them.
Yup, these will be autocad files,..
-
@gjacobse said in Pre-Planning new domain and environment:
But - I have every intention to do right by Enterprise IT standards.
If this is the plan, then how do you intend to deal with the owner making IT decisions that might run counter to that.
-
@gjacobse said in Pre-Planning new domain and environment:
I respect the owners stance, but wont have that information until then... and from that stand point, not important right now.
But - I have every intention to do right by Enterprise IT standards.
If the owner is giving requirements like - files must be stored locally onsite ...
These these two statements don't really mesh.
-
@scottalanmiller said in Pre-Planning new domain and environment:
@gjacobse said in Pre-Planning new domain and environment:
But - I have every intention to do right by Enterprise IT standards.
If this is the plan, then how do you intend to deal with the owner making IT decisions that might run counter to that.
Exactly!
Now, it likely will be that local storage for these CAD files will be necessary for performance issues, etc... but he shouldn't be mandating/requiring this. He shouldn't care where they are stored.
But something like - personal need to have 15 second load time for 1 GB files because we are looking to reduce wait time of our staff, as that wait time for files to load costs us money... then we're setting the expectation without setting the how, because he shouldn't give a shit how it's done.
-
@Dashrender said in Pre-Planning new domain and environment:
@gjacobse said in Pre-Planning new domain and environment:
I respect the owners stance, but wont have that information until then... and from that stand point, not important right now.
But - I have every intention to do right by Enterprise IT standards.
If the owner is giving requirements like - files must be stored locally onsite ...
These these two statements don't really mesh.
Exactly, that was my point.
Your owner should be saying "We have X work to do, what's the best way to do it to meet our needs?"
Instead he's saying "Ignore our needs, do it this way, because doing it this way is more important that doing what's best."
It doesn't mean he doesn't have the right answer, it just means he is approaching it (and telling you) as a hobby, not as a business. A business primarily cares about what's best, and only considers other things when they don't negatively impact that. A hobby cares about something else more and only avoids it when it impacts finances too much.
-
@Dashrender said in Pre-Planning new domain and environment:
personal need to have 15 second load time for 1 GB files because we are looking to reduce wait time of our staff, as that wait time for files to load costs us money... then we're setting the expectation without setting the how, because he shouldn't give a shit how it's done.
Even that should have dollars and cents on it, not a hard requirement. It's better, but it's still treating the what as a requirement, just not the how. But that's often almost as bad. What if you could do 16 seconds for 1/4 of the price, or 1 second for only 1% more? Hard requirements on the "how" are horrific, but on the "what" are still bad.
End of the day, if IT isn't tasked with "use business infrastructure to maximize the company's profits", then it's tasked with something else.
