Or are they a tool to achieve simplicity/elegance? Fewer moving parts to troubleshoot at the OS layer, and smaller but more formal composition.
5,758 karma · joined July 21, 2009
Or are they a tool to achieve simplicity/elegance? Fewer moving parts to troubleshoot at the OS layer, and smaller but more formal composition.
Ensure you have enough of the following: Sunlight, physical activity, sleep.
Set a specific time to sleep and wake. Get a step counter and ensure you are getting at least 10k steps a day. Regular walks during the daytime will help with both sunlight and activity.
After that, work on diet and social activity. If that doesn't fix it, talk to a professional.
Costs to get to space will trend downward. Our knowledge of the solar system and it's potential for economic benefit trends upwards. At some point someone will find a way to make money, even if it is a niche application. That early industry will create the infrastructure which will open up other areas of development etc... A positive feedback process.
Corruption isn't only about who avoids punishment, but also who is the target of punishment. In highly corrupt environments you will often find complex and often contradictory rules, that produce a default state of guilt. The only way to avoid punishment is to participate in the corruption.
https://www.synology.com/en-us/compatibility?search_by=produ...
It's not a hard requirement to use Synology drives, but on the newer/higher-end models the options to not use Synology drives are very limited. For example the FS2500 only has four models of SSD on the HCL and two are Synology.
IMHO, the price premium for the Synology branded drives is reasonable. Pay for the validated drives. Maintaining a broad HCL is no small task.
https://blog.synology.com/in-pursuit-of-reliability-hat5300-...
Sysadmin/ops has too many offramps that drain talent before year 10. If you can integrate software/systems well, manage projects or do advanced troubleshooting; you will likely be pulled out of ops. Conversely there are an ocean of security certifications being issued to people who have very little operational/technical experience.
Data security in practice is being reduced to a policy and procedure checklist. It is frustrating for an engineering group to receive non-specific or contradictory policy guidelines written by non-technical people, but I have yet to see that change hiring or decision making. Businesses want someone who will agree to check the box. If that someone doesn't know all the details, that makes checking the box easier.
The future of cybersecurity is not skilled coordinator/PM but instead yet another non-technical management arm handing down mandates that are blind to technical reality. There isn't another option. There aren't enough people to fulfill demand, and the compensation for cybersecurity positions are often less than a senior infrastructure role. How many sysadmins really understand networking, programming, databases, etc; While also having the people skills to not alienate both management and highly technical development and operations teams? We will never have enough people at the intersection of that many skills.
> Has anyone done this and what was your experience?
It works as expected. Big cost/time upfront to get all the equipment setup, then things mostly just worked. The primary challenge is transferability and standardization.
> How do you select a colo and what do you look for?
Bandwidth availability. Proximity to the team supporting it. Reputation among customers.
> How do you manage the hardware and how much savings in time/$ is there really?
Whatever custom stack is built in the colo must be well documented, and have solid maintenance schedules, and change control procedures. The cost savings exists, but it's never as much as you think.
It's difficult to articulate the specific drawbacks. It's more organizational than operational. Imagine that you have a server dropping at random times. The logs say something ambiguous, and now you have to become full time sysadmin to some elusive problem. No one in your organization will want to deal with these sorts of issues, nor will they want you to burn time on it. There will inevitably be other tasks higher on the list. Operational issues gradually build up like other forms of technical debt. No one receives applause for updating the server BIOS over the weekend. Operational discipline/maintenance inevitably becomes last priority.
The costs were mostly paid by the SysOps. In the form of additional phone lines, disk space, maintenance time etc... A user would have to worry about long distance charges.
Re: average people. At the time, there was much more of a dividing line between computer people and average person. Not that you had to be an expert, but you did have to be an enthusiast. The average person would have neither the skill nor inclination/interest.
Not very similar to social media. Closest description would be a combo of 4chan, HN, and sourceforge, but much more local and inward looking. Like comparing a small town bar vs tinder.
"The BBS industry" was so small that the phrase sounds silly to say. Certainly there were official business bbs and larger players but scale was nothing compared to modern tech companies.
The hardest thing to explain now is how novel participating in a network like this was. Prior to large scale internet access, computers were stand alone devices. Networks were arcane company owned things. Having your computer dynamically bring up what others were publishing was new and interesting.
1. Not realistic, but not outside of normal for an management infrastructure/ops position. What you are writing is what you hope for, but sometimes it sends a red flag to potential applicants. The worry many high level people have is that they will be turned into the 'do everything' person. Trim a few of the less directly related requirements off of the description (e.g. Microsoft certification).
2. Yes... but also No. There are a lot of people who push through their careers collecting credentials and turning it another rung on the ladder. Chances are you will get a rosy candidate at some point, who will put in two years of aggressively spending your budget to inflate their resume and then move on. Not that a majority of people are this way, but the filters are set in such a way that this is what you are likely to end up with.
3. Other comments will say 'pay more', but it will be difficult to meet market rates for this skillset when working with local governments. If you can't get approval to raise the comp, instead try to split this role up into a team. Governments won't pay one highly skilled person 250k, but they will pay four people 80k, and one manager 120k.
4. Politically? Find someone with pull, and make sure that it's 'their idea'. Something that they can put on their win list.
Procedurally? Don't boil the ocean. Handle it iteratively. Start with commercial areas and new housing developments. White-glove your initial smaller install and it will create the broad demand from the community to expand it.
Love what you are doing. Hope this helps.
In the best case where you have a technically skilled interviewer and interviewee, there is still the problem of: 'the correct answer is my answer. Even if yours also works, it is not my answer.'
Tech hiring is not difficult, but it requires the following traits in the interviewer:
1. Broad technical skills and the ability to recognize skills in others.
2. Ego is not driving them. No need to be smarter than everyone.
3. Conversational/interpersonal skills to get the interviewee to talk, and to recognize someone who will be a jerk.
The common assumption is that skilled tech people lack interpersonal skills, but in my experience 1&2 is the rare combination.
Titles are cheap. Your existing employer will always want to hand you more work, but not more money. If you are handling the work well, then the pain of not having that role filled is only a memory. Your future employer has an acute problem to solve and is already primed to spend money to solve it. The net result is that (current employer) is much more likely to increase your responsibilities/scope/title. While (future employer) will pay you.
There are absolutely employers who will give significant raises to existing employees, but they are rare.
For example, how many people sit down and decide to become overweight and out of shape? Yet many of us arrive there by default. It is a similar process playing out in employment. Why many people avoid learning and growing. Not that they decided to atrophy, but more that they haven't tried to avoid it.
It's difficult to produce change in others, or to get them to see the rut. If you are self motivated, it's like speaking a different language. We expect the desire to improve to be intrinsic, and that if they have the desire that they will act in a way to produce results. But both are false assumptions. There are those with no intrinsic desire, and those who have the desire, but not the habits/discipline to take effective action.
My best results has been to push them down the path. Set the goals and routines for them. Get them moving fast enough that learning/growing in a specific area becomes part of the routine.
DKIM = This specific email can by verified/authenticated by my DNS.
DMARC = What to do with email that doesn't comply with above. And how to tell me about it (if you want to).
SPF is basically useless due to the centralization of email providers. It was created to be locked to a company specific email server. E.g. Only accept mail from exchangeserver.company.com, and reject everything not from that server. Now everyone authorizes Microsoft or Google to send their mail.
Probably more effective for some restaurant franchise to add EV charging as part of their branded setup. E.g. Every IHOP in the country has EV charging.
Depends on how narrowly. Overall I would consider an amendment strengthening the 2A more likely than removing the 2A.
There are relatively few states with strict gun laws and more constitutional carry states every year.
How do we improve this common scenario? What are the root causes?
The common themes are:
1. Lack of technical project competence at the decision maker level.
2. Scope creep. Where the one true system has to do everything.
3. A 'one-pass' approach where everything is expected to be delivered as a working system at the end of the project.
Even fixing two of these gives us a solid shot at a successful project.
However, EV's still win by a large margin. It's a lot easier to make one big powerplant clean, efficient, and cost effective rather than a million little engines that have to make tradeoffs for weight/size/performance etc...
Imagine how much it cost them to build up and tear down development teams six times. Not just in real costs of contracts and such, but also the logistical costs of training the new teams, building the relationships, finding faults, correcting errors, determining alternatives, knowledge transfers, etc... Not to mention opportunity costs of all the time spent.
Effective outsourcing is paying AWS/GCP or Heroku for whatever they can provide. Not trying to turn an expensive employee into a cheap one.
Yes. The person I was replying to seemed to assume that college was where people are disabused of idealism. My response was satirical.
True; college students are noted for their lack of idealism.
Conversely right leaning occupations such as veterans, oil rig workers and farmers always have their head in the clouds with high minded idealistic notions that don't work in the real world.
If they won't budge on compensation, accept the title and add it to your resume. Start looking for better offers. If you find a better offer, then they were wrong about market rates.
"People don't want a drill, they want the hole"
Talk to your intended audience to figure out what they want to accomplish, not just the tools they ask for.
This is a useful way of looking at things. Yet, there is a limited distance we can expect the audience to traverse before using what they are familiar with. The number of fax machines in existence shows the staying power of habits.
As a startup, look at the decison/control points specific to the 'job to be done'. This is a game of revealed preferences and principle-agent problems.