|
Sure, but our MoD wouldn't accept an offer from an "economically disadvantaged" company. They require documentation of longevity/tenure, proof of assets, and evidence that sufficient resources can be applied to the contract.
It's the MoD, not the guy down the road who runs the post office and needs a spreadsheet app. You have to prove that you can deliver and that you'll still be around to fix it, n years down the line.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
Officially a small business setaside, with all the box ticks that charlieg listed acting as boosters in the selection process. From what it sounds the company is a parasite that will effectively skim off a passthrough for administering as many of JSOPs coworkers as they end up hiring when taking over. The company in question was competing to administer the existing workforce after takeover not to provide a new one. 
And yeah it's not uncommon for positions where the DoD has contractors running onsite operations for it. 
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, waging all things in the balance of reason?
Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful?
--Zachris Topelius
Training a telescope on one’s own belly button will only reveal lint. You like that? You go right on staring at it. I prefer looking at galaxies.
-- Sarah Hoyt
|
|
|
|
|
I forgot to mention that we can't even get to the company web site from work...
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
|
|
|
|
|
John Simmons / outlaw programmer wrote: I've already GOTTEN half a dozen headhunters contacting me letting me know that the position I currently hold is available.
That is bizarre 
|
|
|
|
|
...and a completely unnecessary abuse of the English language.
cheers
Chris Maunder
|
|
|
|
|
Suck it, Maunder.
BTW, is CP hiring?
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
|
|
|
|
|
With an attitude like that I'm almost certain either you won't be receiving a message from @chris-maunder saying that you've GOTTEN the job, or that you have successfully completed the interview post and GOTTEN an offer as Sean's minion and full time mankini cleaner. 
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, waging all things in the balance of reason?
Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful?
--Zachris Topelius
Training a telescope on one’s own belly button will only reveal lint. You like that? You go right on staring at it. I prefer looking at galaxies.
-- Sarah Hoyt
|
|
|
|
|
you forgot the italic tag.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
|
|
|
|
|
John Simmons / outlaw programmer wrote: BTW, is CP hiring?
I couldn't imagine a Texan moving to Toronto (as winter's about to start) and liking it.
|
|
|
|
|
John Simmons / outlaw programmer wrote: I'm probably going to switch over from my typical cheery, sensitive demeanor, to someone that is more surly, short-tempered, and just plain rude.
cheers
Chris Maunder
|
|
|
|
|
A few decades ago something similar happened during the commissioning of the (then) new Denver airport. They had a bid from a competent company to develop the software for the baggage handling system, but decided to give the contract to another, utterly inexperienced company to satisfy affirmative action requirements. Why not? Programming is just typing and any moron can do it, not so? 
The end result: The opening of the airport was severely delayed, by more than a year as far as I remember, and in the end they had to go back and appoint the competent company, who saw them coming and made them pay through their noses, because getting the baggage system to work was now a crisis. I love this story!
Get me coffee and no one gets hurt!
|
|
|
|
|
This story raised a little bit my faith in the Universe!
GCS d--- s-/++ a- C++++ U+++ P- L- E-- W++ N++ o+ K- w+++ O? M-- V? PS+ PE- Y+ PGP t++ 5? X R++ tv-- b+ DI+++ D++ G e++>+++ h--- ++>+++ y+++* Weapons extension: ma- k++ F+2 X
If you think 'goto' is evil, try writing an Assembly program without JMP. -- TNCaver
When I was six, there were no ones and zeroes - only zeroes. And not all of them worked. -- Ravi Bhavnani
|
|
|
|
|
Cornelius Henning wrote: I love this story!
I don't think it's exactly true. 
http://calleam.com/WTPF/wp-content/uploads/articles/DIABaggage.pdf[^]
The company hired to create the baggage system was BAE Systems - a huge multinational corporation of over 80,000 employees - not an affirmative action charity case.
The problems at DIA were way more than software and the ultimate "solution" was not hiring a competent software company - they reverted to a "manual" system that still runs today.
In this present crisis, government is not the solution to our problem; government is the problem. ~ Ronald Reagan
|
|
|
|
|
Thanks! I told the story the way it was told to me.
Get me coffee and no one gets hurt!
|
|
|
|
|
This is the way government eventually fails.
New guy: "Hello, I'm new here."
Incumbent: "Great, this is the way we run things, as it was relayed to me."
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
|
|
|
|
|
Traditionally, I've been a Linux/Shell/Bash disliker. I had completely grown up on Windows. The last thing I loved on a black screen was DOS. Though I still use Windows Command prompt, and those techie C# Console tools I write.
The windows chain of tools & utils has been so productive with drag n drops,click-clucks.
Now unfortunately I'd been often forced to look into Linux
I had suffered enough because of my Linux-ignorance, losing some of our valuable customers.
(Yes we should ideally hire a Linux admin, we have that in the To-Do for an year.)
Linux environment, I simply couldn't take it. It brings so much fatigue to the brain if I'm continuously traversing like, Okay to do this, do that. To do that, install this. to install this, install that. For that, type this. And finally I realize, what I have is a bare naked system. And every damn thing has to be manually set up. How unproductive this is.
It's a total fatigue. May be it's because I've identified myself too much with windows and nothing else. I don't know.
Now I'm at a point to give it a try again. I believe I can Sit down and learn all those things that I see on a dry linux Book. I believe I can still do with so much eye sore.
The question is, is that any worth? Or the linux world is by any chance moving towards GUI, click-cluck direction. I've seen ubuntu desktops and got some sigh of relief- okay, may be it's time we learn some linux stuff! (with mouse)
but what I'm talking about is Server. you think, Linux _SERVER_ . Is this always going to need Shell commands expertise. Will there be something like remote-desktop, Click to deploy etc coming up.
If Linux is just going to stay with Shell prompt and commands, and nothing new coming up, then I should give a try again. this never ending story...
Starting to think people post kid pics in their profiles because that was the last time they were cute - Jeremy.
|
|
|
|
|
Have a look I think you maybe surprised, its moved along a lot since you last used it in, I would guess the early 1990's.
Start with the Ubuntu desktop distribution.
|
|
|
|
|
Thanks. but I'm asking about Server editions.
Starting to think people post kid pics in their profiles because that was the last time they were cute - Jeremy.
|
|
|
|
|
Vunic wrote: If Linux is just going to stay with Shell prompt and commands, and nothing new coming up, then I should give a try again. this never ending story...
Well... I work for a company quite uptodate and innovating (technologically speaking) and I have to do with Linux Console servers and some web based apps that helps the other people, but through console I can do more things and even some tricks that are not possible using the click-tools.
I started with linux around 18 months ago and I am far from being an expert, that's why I am very careful and don't do things where I am not sure about the result... but it is not bad as I thought before starting and have already built some things where people working there longer have told "nice"
In my opinion... interfaces as Ubuntu are fine for private users, but I don't think is going to get into Server side so fast, they still need a lot console to be configured, changed, secured and other staff.
If that is enough for you to start learning it or not... is another question.
M.D.V. 
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
Vunic wrote: Is this always going to need Shell commands expertise.
Yes. And editing (in a text editor) whatever obscure configuration "language" your particular choice of server poison is, often several, as typical configurations have multiple pieces "working together."
Vunic wrote: Will there be something like remote-desktop, Click to deploy etc coming up.
My suggestion:
Create a VM of a baseline system, get it configured the way you want, and clone it to replicate it elsewhere. I suppose Docker might be useful for that.
But:
Document every step you take! Every shell command you enter. Every configuration change you make.
When you've done it once, start from a clean slate again and try to replicate those steps.
When you've successfully replicated the setup, put the steps into a .sh file, start from a clean slate again, and run the .sh file and see if it works.
Keep a journal of useful commands, creating a quick reference guide for yourself.
Hiring a Linux admin is great, but they tend to be biased, they don't document anything, and the next admin will complain about how stupid the previous admin was. If you hire a Linux admin, make him document, make him test his scripts, make him prove his scripts work. (I don't know any "her" Linux admins, so forgive my bias there.)
Think of a Linux admin as a black box that you need to "unit test."
Linux desktops suck. All of them. You will find yourself using the shell because the desktop UI doesn't provide what you need to do, and is klunkier than the shell, hard to believe!
Marc
|
|
|
|
|
You are a pragmatic cpian. Reminds me of Chris@(Christopher Duncan, I'm not sure if he's active here) Thanks for the wonderful reply. I'll keep them in mind for sure.
Marc Clifton wrote: Document every step you take! Every shell command you enter. Every configuration change you make
This is unbelievably needed. For every command, I google, type it, something runs and I move away from it. This has been a major problem in grasping the commands. I didn't seem to store them in my mind as it was just running out of a copy paste. (Linux' copy-paste : See through your sore, naked eye and type it again through your sore naked eye + 10 naked fingers)
Marc Clifton wrote: I don't know any "her" Linux admins, so forgive my bias there
So true. 
Starting to think people post kid pics in their profiles because that was the last time they were cute - Jeremy.
|
|
|
|
|
Vunic wrote: and I move away from it.
history has saved my arse a few times trying to remember what I did.
But yeah, I started that way too--type something, it worked, move on. Then I realized, crap, I have no idea how I got the system working.
The next step, which I still have to take, is to actually read the documentation for that obtuse command I found on SO.
Marc
|
|
|
|
|
Marc Clifton wrote: Document every step you take! Every shell command you enter. Every configuration change you make.
Damned good advice. I've several times managed to configure things in linux, but then never been able to find how I did it.
Marc Clifton wrote: When you've successfully replicated the setup, put the steps into a .sh file, start from a clean slate again, and run the .sh file and see if it works.
... And then build a little GUI for it, with buttons and places to enter values...
... Oh, wait! That would go completely against the principles of linux!
Instead, split it up into 368 smaller files, distributed all over the HDD, that you have to edit manually, and which are then assembled by a map file that needs fifteen frameworks to run.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
Mark_Wallace wrote: Instead, split it up into 368 smaller files, distributed all over the HDD, that you have to edit manually, and which are then assembled by a map file that needs fifteen frameworks to run.
At which point you can claim the title "Linux admin."
Marc
|
|
|
|
|
Marc Clifton wrote: Document every step you take! Every shell command you enter. Every configuration change you make
That's the best idea. This way you create a methodology to the entire thing and it makes it far more memorable too. And, this way you can document things you did try but decided against.
Great stuff!!
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
