Eric Schmidt is working to launch a university
businessinsider.com
businessinsider.com
This is far from true. If you look at the total workforce in tech, the majority is by far from much larger, public schools, like Berkeley, Michigan, Illinois, Washington, Texas, Wisconsin, etc., etc. MIT and Stanford have had amazing great people, but they are far from the "primary" source of talent.
(yes, a bit of an aside, but it rankles)
Which is funny because Silicon Valley companies won't think candidates from those schools are that interesting, while simultaneously thinking that the intelligence and defense has better programmers. People are people.
I don't even think it's ideological. The reason the defense industry lacks top tier talent is because it's quite literally the most stifling and frustrating place to work possible. You're mired in endless bureaucracy, incompetent management, arcane rules and regulations surrounding secrecy, and some of the world's least flexible working arrangements. It ends up being a great place for people who want to punch a clock and get a reliable paycheck, but a deadend for anyone trying to make their mark.
-- KH-11 satellite, and presumed successors
-- Stuxnet
-- Utah data center (https://en.wikipedia.org/wiki/Utah_Data_Center)
-- The rather enormous intelligence budget that allows all kinds of creativity
The above indicates that there must be some corners of these agencies that are extremely technically skilled, and able to do real stuff with breathtaking ambition. Given the budget, these "corners" might be pretty big, and attract some excellent talent.
Those that know, aren't talking, and those talking (ahem!), don't know.
For one, GPS was created by the DoD and I am still blown away that it is so good, accessible, and free for consumer use.
Pretty hard to argue with that list.
A friend of mine (who went to NMSU) worked for NASA. He wrote the code that determined what angle the solar panels need to be at to get the right amount of sun to power the ISS. Crazy number of edge cases, and people die if you have a bug.
Was pretty impressive to hear the things he had to do and the processes they had for minimizing the risk of someone dying. I'd put that on par with many things, too (although Stuxnet has its own place for genuflection).
Stuxnet was probably mainly Mossad.
The Utah data center was a pretty run of the mill data center, but apparently plagued by technical issues.
And yeah, they have a huge budget which allows them to buy a lot of toys for a bit above normal price.
Their mathematicians are top notch though from what I've heard.
You're right on the money for math though, crazy smart mathematicians.
But if you're a programmer without a scientific speciality, then there's less reason.
The contractors have some freedom to pay as they see fit -- they pay more than the national labs in my experience -- but they still have to justify their rates to the government during contract negotiations, and the government can push back. The pay is "ok", but has been falling increasingly behind "Tech". So now there's brain drain, particularly among programmers.
My impression is that if you do work directly for federal or state government, you also are likely to be alongside a substantial number of contractors.
Reality Winner was a contractor, by the way: https://en.wikipedia.org/wiki/Reality_Winner
Multiple programs were built to fix the compensation for military members whom were paid even less than civilian counterparts in the same offices. It's why the churn rate is so high. Even then, the majority of cleared jobs still aren't commensurate with external salaries.
I’m not disparaging the nsa etc talent, but it’s very hard to arrive at fair comparisons in this area.
The sec teams at faang are just not tasked with stuff the nsa does.
Not that any specific set of their employees are super geniuses.
While SV still has to run a profitable business while trying to care about security.
Along with sovereign immunity to CFAA and other laws
1 Massachusetts Institute of Technology 3,130
2 Stanford University 3,444 ' 3 University of California--Berkeley 2,337
4 California Institute of Technology 536
5 Carnegie Mellon University 4,112
6 University of Michigan--Ann Arbor 3,247
7 Purdue University--West Lafayette 3,428
8 Georgia Institute of Technology 4,252
9 University of California--San Diego (Jacobs) 3,141
10 University of Illinois--Urbana-Champaign 3,736
https://www.usnews.com/best-graduate-schools/top-engineering...
For comparison, GATech claims 61% of their students get engineering degrees and an enrollment of 14,142, thus ~8,626 undergraduate engineering students.
https://coe.gatech.edu/about/facts-rankings
Other school's engineering enrollment:
UT Austin claims 6,003 undergraduate and 2,101 graduate.
https://www.engr.utexas.edu/about/facts-and-rankings/program...
Berkeley claims 3,746 undergraduates and 2,357 graduates.
https://engineering.berkeley.edu/about/facts-and-figures/
MIT claims 2,451 undergraduates.
https://engineering.mit.edu/about/facts-and-figures/
Stanford claims 1570 undergraduate and 3603 graduate.
https://registrar.stanford.edu/everyone/enrollment-statistic...
I think the parent comment is correct to say there are many larger engineering schools than MIT and Stanford.
https://eecs.berkeley.edu/academics/undergraduate/eecs-cs-co...
I think what they probably meant talent pools for some companies in the tech industry, or something similar.
Once a candidate gets to me as an interviewer, I'm mostly looking at a resume for what topics I should ask about, both things that you're comfortable in, and things that you're not. If you have personal projects, I'll ask pertinent questions about them, and often I've learned some very interesting insights from the personal projects of candidates.
In my time interviewing, I've hired people without degrees as senior engineers and I've rejected people with doctorates in computer science as junior support engineers. Turns out, degrees are a mediocre predictor at best of ability to do a job, and practical experience is 99% of the time more impactful than a piece of paper.
That's interesting, and somewhat rankling - as both times I interviewed at the G in FAANG, not a single interviewer gave a nickel about any of my experience, or projects I had worked on.
It's such a joke that the keys to a golden line on your resume and a giant salary are gated by the luck of which 7 people get picked to grill you that day, how busy they currently are, and what their pet question is.
Job hunts are a campaign. If you're pretty good you'll land a job but you might not land every job.
While this varies from company to company generally resumes get you interviews and interviews get you jobs.
Even if you have a 95% pass rate for any one interviewer, you're at like 77% for passing a 5 person panel. Good but hardly a guarantee.
But if you have even three job interviews, the chance that you'll get atleast one is 98.7%. Not so bad!
Sure it's a bit hand-wavy but I hope it takes the edge off this interviewing business for you the way it does for me.
Cheers!
Moreover, I'm not really interested in "years of experience". Previous titles don't really matter, too.
What does matter for junior and middle developers: personal projects, specific products or features developed by them or their team, accounts on Upwork, GitHub or StackOverflow, recommendations from other people, a personal website or a blog.
We are talking about the initial screening filter, so _anything_ proving you are a real developer is fine.
Since there are currently 23 IITs, the numbers that go to US (and SV) every year can be very significant. The long term effect of this phenomenon can be observed from the increasing number of US (and SV) tech companies CEOs are from India education background.
These schools are very good btw. Berkeley is tied with Stanford for example, UI #5, Washington #6, UT is #10.
Conversely Harvard is ranked #15, but that's the things about rankings: they're often used to prune out people who don't "know someone", and when the metrics do not match someone's perceived "elite" status, they are ignored.
All of the schools you mention are attended by elites and commoners, produce talented people and untalented people, jerks and kind folks, and all the permutations of that.
I just wish we'd focus more on competent and kind, and less on connections or wealth - companies that do this will prosper IMHO, and companies that rant about "meritocracy" will wither as they drive away half the population.
Women are just as capable of coding well - creating a toxic culture is reducing your talent pool by half, something people obsessed with "facts and logic" should think more about. Insisting on "elite" schools when the good ones are public will also harm you long term if you're doing more cutting edge stuff.
>haven't built universities like Stanford, Duke, Cornell etc.
I assume the answer is that they generally find that it makes a lot more sense to give oodles of cash to their alma mater or some favored school to get your name on a building and/or really beef up a department than to try to found a new school which would likely take decades to establish any sort of reputation.
(Although that might make sense given the mission.)
That's the rub though, isn't it. I'm not sure even Bezos has money that would be needed to pull that off over, say, a 10 year horizon. MIT has almost a $20 billion endowment to give some idea of the sorts of money flows we're talking about here. To say nothing of the fact that they already have the faculty, physical plant, reputation, etc.
He is barely 10% of Jeff Bezoz. Not just a name on a building either. A whole new program.
Bezos would be dead long before that happens.
- Desired faculty: We'll triple your salary and hire your spouse too. Oh, and give you unprecedented freedom.
- Desired students: Free tuition and board and a great campus environment.
At the least you could jump-start a pretty darned interesting educational institution at least within a certain focus. But I'm not sure the money is realistic, at least at a scaled undergraduate level.
We’re talking graduates who become heads of governments, CEOs of unicorns, etc.
Now you could become “the Harvard of tech” a bit easier, but would Bezos settle for that alone?
The chances of people not knowing what MIT is or their reputation going down is very low. And that’s a big reason why people want to go there.
They have sort of become Billionaires playground.
But the point of Olympic medals is to assess skill. If the available pool of talented athletes is larger than the number of gold medals, then there is a need for more gold medals.
Different fields have different balance between these two things.
http://induecourse.ca/the-bottleneck-in-u-s-higher-education...
"That kind of school" is (call it) a Top 10 school in a given field. And there is always going to be a shortage of slots at Top 10 schools whether you have 1,000 schools or 10,000. What potentially makes sense is investments in relevant subject areas in schools that aren't in the Top 10 but are in the Top 100 so they're functionally less distinguishable--except in prestige perhaps--though arguably that's already the case. In the US, cost aside, a qualified applicant can already get into a "good" school.
For schools, like Harvard and Yale, isn't a large part of the value they provide to students derived from the school's network of alumnus and the prestige the school's name holds? If so, don't these schools derive a large part of the value they offer from their exclusivity?
The Morrill Land-Grant Act was, in part, a response for the need for new skills of an industrialized economy.
However, if you believe schools are mostly about credentials and signalling, online learning institutes often have a large accreditation hurdle. E.g., it's generally preferred to have an MIT degree rather than a list of MIT MOOCs taken because there is a certain amount of elite signalling that comes with the degree even if the skills learned are the exact same
From my perspective, it is also much preferable to have an actual degree from Plymouth State University, or even an online degree from Southern New Hampshire University, than a MOOC "degree" from MIT, and I strongly disagree that the "skills are the same" in practice, evne if that might be true in principle. It's not just about elite signaling, there are huge differences in rigor, workload, and personal responsibility with an actual university education versus a MOOC.
MOOCs are fine to supplement a bachelor's education, but if I saw a resume that only had edX/etc, they'd better have good work experience or a great project portfolio.
In my experience, this even holds true for the same degree within the same institution across different timelines. There’s other pressures (financial, political, etc.) that can drive rigor and curriculum to change. That is at least part of why accreditation is important; it’s supposed to provide some third part vetting that the product is meeting minimum standards. (Again, in theory).
I think it will get much more interesting if online courses can fix the quality/accreditation disparity. With colleges no longer having a monopoly on education that’s still their strongest chip to play
This is a claim I've seen repeated often but have never seen any real evidence to back up. It seems more like "we need skilled workers but don't want to pay them skilled wages." Regardless the problem (in the US) is not an absence of universities like it was in the 19th century - financial barriers to bachelors degrees are significant but that is not a symptom of low supply and high demand.
So no, I don't think the demand exists (in the US) today, at all.
As a nice bonus, why not turn it into a basketball powerhouse school too, something to help brand the school, like Duke or Stanford. Something MIT is missing.
Hungarian PM recently kicked them out of Hungary, so it moved to Vienna.
[0] - https://www.ceu.edu/
By contrast, in Germany there are no universally notable private universities at all (save for some business schools).
Not to point out the obvious, but 2 of your examples never bothered to stay in undergrad university long enough to get a degree and they managed to succeed beyond all of their contemporaries.
Perhaps it says something about our current university system/paradigm that the current wealthy have chosen not to support this route. Or maybe it says more about the Gilded Age robber barons that they chose this route (in addition to the large inheritance fortunes they left).
Marc Andreessen's "Build Stuff" article[1] pointed at the lack of university capacity in the USA (I doubt this is accurate[2]), but leveling up the average university to be closer to the top tier universities would certainly help or at least justify the current cost of university.
[1] https://a16z.com/2020/04/18/its-time-to-build/
[2] https://www.quora.com/How-many-college-students-are-there-in...
Contrary to popular belief, established universities do a very effective job of preparing tech talent for government jobs. The issues, which Schmidt seems to miss, are twofold:
(1) the government, with few exceptions, is a TERRIBLE place to build effective tech skills. Slow, heavily outsourced, bureaucratic beyond belief, and low paid, there is very little creativity and variety in which to build unique technology, and no reward for the BS.
(2) Current universities already prepare tech workers well. In some cases, there are even joint CS-Public Policy degrees (e.g., MSCAPP at UofC).
Those engineers with policy expertise just don't want to work for the government. I know; I was one of them, and I could not for the life of me find a policy tech job that paid even HALF what tech companies would pay me.
Schmidt should focus on building "the department of innovative technology" and pay engineers appropriately.
Strong claim; links or citations to back it up? (Not necessarily doubting you, but it sounds a bit like a right-wing talking point, and hence I ask)
You're right about pay problems, though. With public sector jobs, you have to do it for the calling, not the bottom-line cash (imho).
What you see: a bunch of tech startups founded by ex-Google, ex-FB, ex-Amazon employees.
What you never see: hot tech startups founded by ex-government bureaucrats
At very best/worst, you get beltway contractors who have "skills" at extracting money from the government. Those contractor firms NEVER end up selling back to private industry, because they have nothing to offer.
I think that this is one of those cases where "citation needed" is a way to avoid the blindingly obvious truth of the statement. No, we haven't done a controlled experiment on the government vs private enterprise in skill creation. Sometimes you have to use common sense and obvious experience.
I've found tech maturity is more a function of age and context than public/private.
Many government employees are motivated by different factors. Somebody who is motivated by pay would likely gravitate towards the private sector and starting their own business. Somebody motivated by service may be more apt to apply to government jobs. For instance, I would seriously doubt mathematicians who work for intelligence agencies are lower-skilled; this is probably an occupation that selects for other traits.
I am also aware of a LOT of former government employees who start their own companies but it's not clear how much of their success is due to skills vs. network effects.
Long lead times don't go well with the pump and dump vc funding model.
Having to deal with overwhelming bureaucracy in exchange for working on what everywhere else would be legacy systems really killed any desire to stay.
Kind of like SpaceX popularizing rocket reuse, we should think of older code, languages, and frameworks as "battle tested", not "legacy". They should only be replaced if it's clear that essential maintenance is not possible, if a critical requirement isn't being met by the old system and will confidently be met by a new one, or if it can be demonstrated that a new system will save more money than improving the old one.
I do agree that many organizations accumulate so much cruft they have trouble getting out of their own way. But the flip side of rewriting things for reasons isn't necessarily better.
This, I guess, would be a consequence of legacy bureaucracy, given that the people making the calls are not very aware of the new technologies and their advantages. A reluctance to adopt Python for example out of a distrust of FOSS comes to mind.
https://www.youtube.com/watch?v=DvXN7fRTVds
I think you're misinformed on the topic, but that's OK. I assumed it was a typical government agency until I got further information, and then I changed my mind. Will you change your mind?
It is not a lack of talent, it is a lack of good governance/administration that causes most software/IT failures for the government. USDS is actually pretty cool, and they seem to be doing really great work. But they're a small part of the system. In order to actually improve software/IT within the government we need to fix a lot of small problems.
Here are some more:
Just the universal waste within the way government treats software acquisition. If you ran a private company and you had small teams (each less than 10) going out and individually buying a software system, say half of them end up buying small-team licenses for Visual Studio as an example, you'd want to murder someone. They could save 20-40% by combining all purchases under a common contract.
Or instead of hiring an actual system administrator, the new guy gets tasked with managing in-house servers. Oh, but it's not one person for an office of 1k, it's every small team of 5-15 people dedicating one person to manage 1-5 servers. Servers that could, mostly, be shared across teams and so instead of 100 admins you could probably get by with 10-20 full-time and trained admins, along with a fraction of the servers and a fraction of the software cost.
The US government does this all the time because there is little-to-no communication involved. What's hilarious(ly sad) is that I've seen this where the purchases went through the same purchasing officer. A bunch of teams all buying expensive (because of scale) licenses when they could've combined them into one joint contract. Millions wasted a year doing crap like this even in smaller branches.
Fix the crap like that and then USDS's model can become effective and universal. Until then, there is so much waste abounding within the way US government does software/IT that it will always be a joke.
Some good things here: (1) It's good to try to solve problems. (2) There is a shortage of tech talent in the country (3) Eric Schmidt is very smart. Sure as heck smarter than me.
Still - from my admittedly-limited vantage point, I can name a four people with degrees in public policy and CS (or similar) that tried and failed to get good jobs in government, so they took $150k+ tech jobs in the private sector instead. So seeing someone saying "the problem with government tech is one of pipeline" is jarring to say the least.
I do see value for an institution described as such in this post, but much more on the research side of things with a secondary focus on should a new branch of the military be established to focus specifically on cyber issues, such an institution could become valuable in the same vain as something like west point.
Schmidt failed to consider the perspective of one of the key stakeholders in the area he's trying to change. His idea would get laughed out of the room if he wasn't already a billionaire.
Just because people love to point out the HN discussion where Drew Houston got scrutiny for Dropbox, doesn't mean that discussion isn't valuable. I'm sure as hell Drew learned a ton from the criticisms.
This is the point of HN - it's OK.
If we discourage people from trying 1/100 or even 1/1000 chances because it's overwhelmingly likely they fail, we miss out on the massive upside offered by these risks.
Perhaps one of the goals here is to flood the government tech sector with new personnel who have been indoctrinated to expect a certain culture, in such a way that the existing structure won't be able to resist changing. If you and your entire cohort have an n-year commitment, and all of you are saying, "No, this is too slow, don't outsource that we need to do it ourselves, that's not the right tech we need to use this," eventually something gives.
Currently a public sector tech worker, although in Canada. We can recruit some great people as although the salaries are not FAANG, they are pretty good for people who don't live in cities with that.
Problem is, they don't give raises or if they do, the raises are tiny. I earned 10,000 more choosing a government job over other offers where I am. I have been in the role 11 months. Recruiters are consistently offering 10,000 more than what I make now. Guess how long the average person stays? Just over one year.
If I quit my current department and went to a different government, I could get that 10,000 dollar raise and if I quit after another 1-2 years there to another government department, I would probably hit near the maximum bracket for tech work in the government unless I took a lead position.
Government also doesn't recruit people out of school for tech unless they have a full slate of internships. You need at least one year of experience to join. So there is this narrow 2-3 year in your career window where government work can make sense.
So not only are you kind of forced out fairly early in your career, but they incentivize spreading your time among many different departments as that is the only time you can get a big salary jump.
Plus all the other things you say are true. Decisions take months for anything.
I'm sure ES also has a vision for a modern university that has merit, but I'd be skeptical if it was about more free inquiry and public service - probably more alignment with industry.
Google execs often couch their plans with claims about how it's going to be good for the world, especially partnerships with the government. For instance, the takeover of Moffett field to provide a place for the founders to park their jets, as well as space for the new Google HQ.
I don't disagree with any of your points. Cornell Tech in NYC is arguably an example of reimagining things with at least a somewhat clean sheet of paper but I haven't studied it in any detail. One thing that is probably be clear is that there's too much stovepiping in universities in general. MIT's new interdisciplinary Stephen A. Schwarzman College of Computing is another example of trying to bring more disciplines under one roof.
A more straightforward solution would be to just create a new payscale (say, the Executive Technical Service) for IT professionals and other technical domains where federal compensation lags the private sector. The Senior Executive Service (the payscale for senior leadership like department and agency executives, including most political appointees) has about 8000 members- if you gave this system twice as many people and paid them all $100k more than the GS system would, you'd increase the federal budget by about $1.6 billion a year, or 0.04% of the 2019 budget, almost all of which you'd recover anyway by replacing IT contractors who generally cost the government between $250k and $350k each a year. Unfortunately, this solution would really piss off the big federal contractors, who would heavily lobby against it, which is why it doesn't happen even though more reasonable payscales have been found for federal doctors and lawyers.
You must ask yourself why the government is able to retain word-class managers and jurists despite stiff competition from the private sector. James Comey was an executive at the world's largest hedge fund, why did he quit for a government job where he was making 100x less? Any federal judge could've made a fortune in corporate law, why didn't they choose to? Because there is a sense of prestige and national duty about their posts. Creating a similar status for technologists in government would go a long way towards recruiting and retaining top talent.
If we want to convince people that being a government engineer is worthwhile and respected, starting with students seems reasonable.
Even all of the existing US government tech posts like the USDS and 18F are ultimately there purely to service the needs of a bureaucratic agency and their particular management.
For a technology specific role to have the same level of prestige as someone on the federal bench or leading the FBI, they'd need to be giving them unilateral regulatory powers over the broader technology industry in the country.
The positions that run those missions - enforcing the law, ruling on the law, running Medicare, etc etc - should be more prestigious. That said, if the government wants to have prestigious technical work, it should be more open to taking big swings (in an agile way) on hard problems, but that requires investment and taking risks.
Here's a database: https://www.opensecrets.org/revolving/
Gary Cohn, Trump's chief economic advisor did exactly this[0].
"The chief economic adviser was required to sell his Goldman Sachs shares -- and he did so tax-free and with perfect timing"
[0] https://www.marketwatch.com/story/a-rich-gary-cohn-got-even-...
There are already tons of government scholarship programs with strings attached in the form of post graduation service requirements and other hiring funnels that bring in new graduates. The government's problem isn't hiring new grads it's keeping those people once they get a few years experience. The biggest drain is probably government contracting companies who often offer literally twice the salary for the same work. Combine that with the soul sucking aspects that you would find at any large company and you have the perfect recipe for not being able to recruit and retain qualified mid career people.
It's hard to imagine how any amount of indoctrination in the ideals of public service at a special school will overcome those things without something else changing.
Universities are a longterm project, if a university is good or not, is something you don't really realise while you are there but when you are finished and try to use your knowledge.
But even after it got going and moved to its Cambridge campus in 1916 (significantly funded by George Eastman--as in Eastman Kodak), it didn't really become known as a premier institution until WWII.
See example: https://www.centre.edu/bicentennial/
Government work doesn't pay well, so it will never be as prestigious as Stanford or MIT.
EDIT - previous title had the headline part where it said it will "rival Stanford and MIT"
Sure, an FBI Criminal Profiler earns a tiny fraction of what a google dev earns. But one can take serial killers off the street, and the other just makes ads more annoying.
A Social Worker earns almost nothing, but they get to help the most needy of people get the help they need. A FB engineer earns 10x the pay, but just makes ads more annoying.
A teacher earns almost nothing, but they get to teach the next generation of society. An Amazon engineer earns 10x the pay, but just finds ways to sell you more stuff you don't need.
No one goes into government work b/c the pay, they do it for reasons they find more important.
Any interaction that I've had with a recruiter when considering looking.
Me: "I'm not interested in working on ad tech or a bank, etc. I'm interested in privacy companies, green technology, conservation, etc."
Recruiter: "I have a job with Investment Bank X that I think may be interested in."
That phrase is roughly equivalent to how large corporations thank "essential workers" during the pandemic. It's marketing. It's an excuse to underpay and leave workers without sufficient support.
The meme that never dies. Advertising funded tons of tons of businesses on apps and on web, employed hundreds of thousands directly and created a large economy.
Disclaimer: Former google, current facebook employee, working in ads.
Can you elaborate more on how invasion of Iraq helped in increasing quality of life for an average citizen?
I think the only point, why you are seeing this "growth" is that you have an oligopolic structure which is just skimming money (mainly to the benefit of the 0.1 percenters) without creating any additional value compared to the traditional way of doing advertising? Or how again are you increasing available income with your smokescreen of targeted ads?
EDIT: actually I think wikipedia captured it perfectly https://en.m.wikipedia.org/wiki/Rent-seeking - and no, financing some productive webbusiness (which there are?) with a minuscule fraction of the ad money or following personal spleens of the founders/crazy people is not altering the outcome.
Google display ads takes a fraction of revenue and passes the rest to publishers. Same with audience network.
Digital advertising lowered the barrier significantly to making profit for lots of digital businesses. It enabled lots of physical businesses to get recognition and discovery in one way or the other.
Not sure why this is not clear, but happy to discuss more.
I'm also not sure, if I understand this correctly, but 32% (or 1 third) seems like quite a big "cut" for any service to me - but apparently ratios changed with the internet which allows placing these ads at such a low cost :) https://support.google.com/adsense/answer/180195?hl=en
So, do these "digital businesses" create anything, or just skim money? Just because you've built a network of rent-seekers, this doesn't really change the concept.
Also could you explain how physical businesses actually benefit from the "new kind of ads" in a more concise way compared to the weasel-wording "one way or the other" - is more product sold because of ads in a certain area (doubtful, because ads won't change available income), does the percentage of advertising spend go down, when all business go "online" (doubtful as well, or how can you generate growth beyond the growth of the economy, which is the declared target of most adtechy-enterprises?!). So this is frankly neither clear to me nor apparently to you (nor anybody else I suppose), but these are the hard questions society has to answer, before accepting "adtech" as a productive sector of the economy.
I would go so far to say you have harmed the business models of tons and tons of apps by setting up an expectation that apps should be "free".
Disclaimer: Former Google employee.
The fundamental difference between these things lies in the fact that a lot of government work comes with higher levels of responsibility and ownership in terms of the way in which you want to do your job.
There's tremendous demand to join things like the US foreign service officer program because as these people move though their career, there's basically an unwritten promise that they will have a legitimate impact on US state department policy for the countries they work in. Something that will only really ever be true in the world of government enterprise software work if you're the PM.
(1) you will likely get lots of resources to do things that your typical private sector organization doesn't prioritize, like longer term research.
(2) Nobody thinks a job != your career anymore; you could start out with a few years in government service and get education & experience on their dime, then move into the private sector. As more opportunities to get started get harder to find or aquire, this will be a huge motivator.
Side note, I really hope the tour-of-duty model becomes more popular with techies, and more encouraged by employers. I can see it having numerous bidirectional benefits
http://bitsavers.org/pdf/xerox/parc/techReports/CSL-81-11_Re...
The issue with the US government and software is not a lack of talent (within the country, or even within the government itself). But a poor structuring and assigning of responsibilities and a severely risk-averse culture, paired with the overreaction of a risk-accepting culture occasionally showing up and fucking it all.
There is, or will be, sufficient talent in the US to maintain and develop government software systems. Flat out, people keep going into CS and software engineering degree programs. Programming itself is ludicrously accessible compared to nearly any other technical discipline because the cost of entry is about $200 and time.
The problems that actually need to be resolved:
1. Government employees (contrary to popular opinion) are grossly underpaid for their expertise. This leads many of the best to leave and go to private industry and/or government contractors. Those who remain are truly civic minded, or zombies. Moving away from GS helps here (pay for time in grade), but the alternatives are also severely abused. NSPS paid people for changing positions, so there was a ton of job hopping before it was canceled. Expertise wasn't really cultivated, only the same stupid culture of bouncing between jobs you find in parts of private industry. AcqDemo is somewhat better, but in implementation lost all its potential value. Still better than GS, but only barely.
2. In-house development shops are typically made to compete for contracts in the same way as private companies. This creates some interesting conflicts within the organizations. And a ton of the in-house software development efforts are spent on maintenance, not developing new systems. So a different kind of expertise shows up, but not the expertise needed when truly novel projects start up.
3. The people in charge of the IT and software development efforts are usually inexperienced with IT and software development. They're either straight out of college EEs (CS people are at a disadvantage in many government shops) or career civil servant bureaucrats. The latter rely on those same inexperienced EEs. This leads to an incredibly advantage for contractors to push program offices around because they can come off as reliable experts, until you've been burned a few times. But hit a couple milestones and the civil servant in charge is already promoted out of that position and a new one is left holding the bag when shit hits the fan.
4. Risk averse IT severely restricts development environments even when software is made in-house. This leads to incredible slowdowns and often automation is impossible due to having to develop and test on multiple test/dev network enclaves that are separated even from each other. An example is the typical CCB (configuration control board) process which is a monthly (at best) meeting where, mostly, managers decide what new things can be installed on the network. You want an updated version of VS or GCC? Gotta wait a month. You want to use a common library? Gotta wait a month. And that's on top of the delays imposed by security scans (a manual process, that could be automated if it's necessary).
5. Risk accepting IT goes too far the other way as a reactionary response to the risk averse culture that held them back. Their fuck ups lead to the people in (4) being able to justify their positions and cement their culture.
You have to improve the approach to IT, the staffing of the acquisition offices to have competent individuals in the appropriate fields, not just successful (from a promotion perspective) bureaucrats, and probably increase pay across the board for technical people.
Bureaucracy in a nutshell. I wonder if there is a single country the western world where it is actually efficient...
The US government already does really well at training people for the military, both leaders and fresh high school grads.
Personally, I think we need to stop passing 2000+ bills into law and instead give our technocrats some high level requirements that they can figure out themselves (hopefully in more of an agile than waterfall way). Assigning a technical person micromanaged requirements written by politicians and lobbyist lawyers will never be an appealing or successful formula.
How does training of new people address the established culture that encourages hitting milestones (internal) but not achieving the overall mission? How does training of new people address the fundamental problem of developing and testing using 3-20 separate networks with data sharing consisting of bobnet (sneakernet but Bob is the only one authorized to move data between systems)? How does training of new people prevent poaching by contractors or private companies paying 2-3x the salary? How does training of new people fix the problem of inexperienced (training isn't experience) novices running acquisition programs and getting bullied by contractors?
The fundamental model of IT acquisition and software development within the US government is broken. Training the next generation isn't enough, and universities already do that well enough. You have to break the existing system.
When I said we should look at successful country strategies, I expect those strategies will include things like "don't let legislators and lobbyists be apart of contract details -- only high level requirements" and "outlaw the bribery that you call donating to a legislator's political campaign". Perhaps even change the government worker model to encourage small enterprises within existing government (like USDS, 18F, etc) and empower them to help earlier in the design process -- like during requirements gathering.
Is this to be a real college, with accreditation, or something like "Singularity University" or Udacity or DeVry?
The government- Schmidt is making a recommendation to Congress.
> Is this to be a real college, with accreditation
Yes
We don't allow governments to fail (easily) but startups fail frequently and we acknowledge that both bankruptcy and team failure leads to knowledge that is rare to gather without actually experiencing the failure.
I'm not advocating for anything in particular except to acknowledge this fact.
These folks are going to go to this university that is better than Stanford and MIT (let's assume this mammoth task happens) and then eschew working for big tech paychecks in favor of working for the government?
https://www.va.gov/OHRM/Pay/2020/PhysicianDentist/PayTables_...
Anyway, the point is that the federal government can and does pay significantly more than the GS pay scale to people who are federal employees and enjoy federal pensions. Whether or not the feds will choose to pay that to those who work in technology remains to be seen.
The VA is a whole other land of bureaucracy that plays by its own rules.
I guess my point above is that feds can fix this if they truly wanted to. There's precedent for them hiring people for far more money than the regular GS rate when they need to. It would be impossible to hire a surgeon for $160k, but they need them, so they pay more. At the moment, the government doesn't feel they need to pay more, so they don't. I hope someday that will change and think it's important to educate and lobby the federal government to help them understand this and change their policy.
That's separate from the discussion of what these perverse incentives (eg. pay more to mercenaries than to lifelong government servants) do to morale, capabilities, and institutional knowledge. It gets far worse when the president casually says that we should just fire emergency specialists and suggest we can hire them back on short notice in the middle of an emergency.
I'm not sure this is the best selling point to attract a young & diverse student body, given current world events.
I wonder how they plan to do that.
Though it is longer than presented here. The rest is "...and funnel tech workers into government work".
The news is summarizing itself now!
"Per the report, the Digital Service Academy would serve as a third reservoir for the best and brightest technology workers, but one that would ideally produce graduates imbued with a sense of government duty."
... because places like MIT and Stanford sure as hell don't!
It looks like Schmidt just wants the next generation of students to forgo their dreams of starting the next Google.
I think a better idea to help this country stay competitive is for companies like Google to stop offshoring their operations ... and pay their goddamn taxes like the rest of us.
https://www.theverge.com/2019/12/31/21044662/google-end-tax-...
https://fortune.com/2019/12/06/big-tech-taxes-google-faceboo...
Lincoln Laboratory is often called a "PhD graveyard" for good reason: it's where reject academics who were denied tenure go to die.