First one of these I've listened to/watched. I kind of wish you would do an audio version of these with an RSS feed so my podcast app could download them. Shouldn't be too hard other then the hosting aspect of it.
It's not that college is always bad, it just comes with negatives that have to be weighed against the positives. The standard approach is to assume that instead of going to college (whether at 18 or mid-career) is to assume that the person will do absolutely nothing productive with their free time, accept the same stagnation and all other negatives that come with the educational process, and that they will then compete toe to toe after the one has completed college and the other has just waited for them to finish.
But in the real world, someone ambitious enough to have gone to college for career reasons is also ambitious enough to work harder at their jobs, done a side job, gotten certs, learned on their own, moved on to another job, or so forth. Those are the more realistic actions of the other person that had the option of college. So when making the comparison, you have to look at those opportunities and look at the opportunities from the degree process and weight them in that fashion.
I do like the idea of many smaller posts - but it also runs into the problem of many thing to respond to at once. While I'm no where near as fast as Scott, I can typically type two to three small posts before the OP (or anyone other than Scott) replies to my first reply. So unlike your
I like red.
So do I, but have you considered orange,
no but, ...
you aren't having a real back and forth because you run into the same problem as the wall of text issue. I real time conversation where all involved parties get the information simultaneously, in a forum you have people jumping in in the middle and fleeing, or someone who just throws out 5 ideas, each in their own post before any responses are made, and eventually many people just stop reading anything but the last few posts.
I'm not sure you can solve this problem, but it's just good to know it's there.
But smaller posts make it easier to respond. No matter how much time you have, making it faster and easier helps you. Wall of text in the same situation would mean no ability to respond at all.
I noticed this with how you post back in Spiceworks and I was like, what the hell is this guy doing. But having broken up posts to respond to is kind of nice. It becomes not nice when there are many of them peppered throughout the whole forum page. Then you have to scroll around like crazy to find what it is you need to respond to.
This was my point - in other words both situations lead to the same end, people not reading/responding to posts.
Keep in mind what you are implying here... that there is a post that is so long, that if responded to, people won't respond. So the answer is to... not respond? Doesn't that suggest two things...
Not responding would make it worse, not better - because it would just make the thing that you don't want to have happen, happen earlier?
That the source of the issue is the original post(s) that created a situation where you already don't like the length that it would take to respond to them?
Well frankly, due to the organic nature of so many of our and other threads, anything more than about 30 posts deep become near pointless as almost no new comer will read the entire thread before responding. If you're lucky, they'll read the OP and the last 4-5 posts very likely repeating something someone already said.
But that is the case regardless. Wall of texts just accelerate it.
"what they do" for the other it is "what they have to do and hope you do as little as possible." Keeping lots of cooks in their own
Let's use GoDaddy as an example, short of them not supporting a record type, what's the issue with GoDaddy DNS and registrar in one account - specifically?
That's a good one to look at specifically.
GoDaddy DNS is cumbersome to use and wastes time. This is a vendor issue, not a bundling one.
GoDaddy DNS has a less than stellar uptime track record. This isn't a service they are known for, they don't really care as serious customers don't use it for this.
Under normal operations, non-IT staff should never have access to DNS records and IT staff should never have access to corporate identity records. Using GoDaddy for both removes the possibility of keeping those highly critical roles separate and puts the company in danger of IT running off with the company identity and business people of accidentally taking services offline.
As above, there is no safe means of using contractor support for simple IT tasks.
GoDaddy doesn't offer key DNS related features like caching.
You are either stuck using a single registrar (often not even possible as different registrars offer different domains) or stuck managing DNS is multiple locations. It lowers flexibility.
An outage from your registrar can take out your DNS with your risk mitigation removed as part of the outage. Otherwise a DNS outage can be protected against from the registrar and a registrar outage has no production impact. This is the biggest issue, it creates a whole form of risk that need not exist.
The lead in music was significantly louder than the audio after the lead in. that is bad.
That's been since addressed. Actually both things have. The videos from today (not posted yet) are with a still camera and audio tweaking. My dad does the final edits, and he added the intro music. So hopefully those two things are taken care of in about two videos from now.
I found this very interesting, since I'm switching to IT from education I always saw certifications as state mandated in order to even be considered for a position.
Oh yes, in many cases if you want a government IT job you will require certs. In fact, you'll be required to have certs from other industries. That's the degree to which government IT isn't considered professional. Government IT often pays a fraction of the industry and is not taken seriously. In NY state, for example, top level IT technical positions are often below entry level in pay. So below the professional scale.
So if your goal is "government IT" which is sort of its own thing, you'll need certs from non-IT to even be allowed to be hired. But it's often considered on the fringe or outside of "real" IT.
Keep in mind that while we often use IT Professional, as a term, IT are not professionals. Actual "professional" guidelines are actually considered insulting in IT. The idea that IT could be certified or that university education would be meaningful, the very tenants of professional work, are insulting in IT where things are performance based, not government pseudo-union based. A better term to use, at least in your head, is IT Practitioner, not professional. IT does not function if held to the standards of normal "professions". The education or certification needed for those fields are far too low to be useful in IT. The breadth of knowledge and continuous education needed for IT success are much higher than many other fields. This is why it is not considered polite or appropriate to compare IT Practitioners to something like doctors. The bar for being a successful doctor is embarrassingly low for IT, for example.
@sully93 I have a video from MangoCon 2016 where instead of talking about "what isn't IT" I talk about what it is. I have a recent SAMIT video on separating IT from SE. I'll do one soon on separating IT from Bench.