Hacker Newsnew | past | comments | ask | show | jobs | submit | more throwawayjava's commentslogin

I've had a lot of luck with little languages that have an escape hatch into the implementation language.

My "little languages" always have atomic programs/expressions whose meaning is given by an implementation in the base language.

Sometimes, e.g., when my little language has an optimizing compiler or some fancy semantics, the atomic programs/expressions need a tighter interface than "does something". In those cases, I write down the full semantics of the language and figure out what lemmas I need to prove about atomic programs/expressions in order to prove whatever property I want about the overall language. I then enforce those lemmas at runtime using asserts (or, in the case of termination, wrapper code that enforces a timeout).

This pretty much only goes wrong when "everything" is factored out into the atomic programs/expressions. I avoid these situations by only using "little languages" when I can do something useful and difficult using the semantics of the little language. Most common examples include: automatic optimization, automatic parallelization, and automatic verification/static analysis.

But even when it does go wrong in this way, it's no the end of the world: if everything is implemented in the atomics, then you just refactor the implementations of the atomic programs/expressions into a library, delete the interpreter/compiler, and write some wrapper code.


More importantly, this forces you to create an explicit interface for any code you'd like to reuse between implementations.

Inheritance is fragile for a lot of reasons (see e.g., fragile base class). But the most common failure modes all have the same thing in common: the error happens because a developer fails to realize that there's an implicit interface between two things in the object heirarchy.


> there's an implicit interface between two things in the object heirarchy

I think the tendency to miss this is compounded by fuzzy thinking about class hierarchies. I've lost count of the times I've heard somebody talk about an object of a child class "talking to" an object of the parent class, when calling an inherited method. They think there's actually another object -- their mental model for inheritance is composition. Using pure interfaces helps to quash this kind of thinking.


FOIA headcount and budget info.

Also, pay attention to what the bill/referendum is for. Any competent district will have a website explaining to the public what the funds are going to be used for.

In particular, be careful about voting against bond issues that are placed on the ballot within one or two years of the maturation date for a similarly sized bond. Because those are basically a continuation of the status quo, and voting them down can mean costly deferred maintenance and/or dumb financial trade-offs.

Real example: firing a whole bunch of people this year to pay for asbestos removal in cash money (because the bond issue wasn't passed and this NEEDS to be done in order to use the building), and then re-hiring a bunch of people the next year. Because the bond issue failed and the bond issue is literally the only legal way to amortize the cost of the asbestos removal. So, I guess no amortization, we pay upfront and fire a bunch folks for a year in order to afford it. (BTW, we all know from the software industry what happens when you lay off a bunch of people -- you lose your best folks and it becomes difficult to recruit good people).

Think of it like this: school districts in many states literally can't amortize their capital costs without coming to you with a ballot initiative. By voting "no" carte blanc, you're basically saying "I carte blanc disapprove of my local school district using amortization". Which is pretty unreasonable.


The answer depends on the university.

Most universities only distinguish between "academic" positions and "staff" positions.

At most universities, "Academic" positions are something rather specific: usually only the faculty proper, Ph.D.-holding researchers, and maybe a few other student-facing roles (e.g., librarians).

Here is my quick two-part litmus test that's probably pretty accurate for most universities. Assuming you don't know for certain that you are in the "academic" or "staff" bucket, consider these two questions:

0. Are you a Ph.D. student with some funny title like "research assistant"? You are a student. You are not "staff". You are not "academic". You are a student.

1. Do you hold a Ph.D. AND listed as a co-PI on grants? If yes, you're most likely in an "academic" role. If not, you're most likely in a "staff" role (unless you're working with someone who has a shitload of clout).

What happens often in reporting is that "academic" and "staff" numbers are reported, and we assume "staff = administrative".

See the Stanford numbers, for example. Notice how there's no category for "non-administrative non-academic staff". You're either a member of the "academic" group or you're an "other", and the "other" group is not broken out into "administrative" and "not administrative".

Hopefully, this helps. It's all rather confusing and political and, in many cases, institution-specific :)


I'm always extremely skeptical of this. Fundraising departments tend to claim responsibility for all but the very largest donations when in reality a lot of that money would've come to the school no matter what.


FWIW that can be reasonable depending on the size of the district. Ours has ~4k+ non-admin employees and 15+ physical plants. That's:

* a large enough headcount that you need an HR department,

* a large enough overall budget that you need a CFO and accountants,

* a large enough physical plant that you need (sizable) facilities and transportation departments (with storage space),

* a large enough IT plant that you need dedicated staff,

* a large enough student body that you need a legal/compliance group (open records requests, mandatory state/fed data collection and reporting, etc.),

* a large enough teaching staff that you need nodes whose primary function is coordinating significant curriculum changes across grade levels and schools,

* a large enough community that a full-time community relations person is cheaper than bringing in a PR firm whenever necessary (every dollar that schools spend or borrow comes from a democratic process that schools have to engage with seriously in all but the most affluent communities),

* and several other functions.

For a place with 4k people, that's dozens and dozens of admins. There are basically two options: build a wing onto a school, or build a stand-alone building. Most districts go the stand-alone route because 1) districts can often get cheap/free land anyways, and 2) it's a good idea to leave that physical space for schools to grow in case population increases.

FWIW I did the "look up all my past employer's [X type of admin] to engineer/sales/marketing ratios and compare to the school district" thing. I couldn't find anything out a whack. But the resulting raw numbers definitely mean the district needs dedicated space for admin folks.


> What happened? Undo that.

1. the construction of interstates and airports that routed around old railroad/highway towns.

2. The green revolution. Agriculture became much more efficient, productive, centralized, and automated. See https://en.wikipedia.org/wiki/Agriculture_in_the_United_Stat...

3. Resource extraction running its course.

4. Efficiency improvements in manufacturing and resource extraction.

The amount of rural blight caused by the favority political demon of late (outsourcing of manufacturing) is relatively minor compared to the above items. Especially 1 and 2! (Seriously, if you come across a run-down main street away from any interstate, odds are better than even it used to be a railroad station.)

IF we follow your advice in a way that's meaningful to most rural communities, we'd have to roll back the green revolution, bring back passenger rail, and magically refill coal veins/oil wells.

Other favorite policy quick-fixes as of late (in particular, on-shoring manufacturing) might help a handful of communities but are a teeny, tiny fragment of the story for blighted rural america in general. The ~80% of small towns that never had a factory to begin with can't reasonably blame outsourcing for their woes.

> It should be even easier now, given that a little remote office can be easily connected to the rest of the world.

1. Have you lived in rural America? Especially outside of "technically rural" locations such as university/college towns, good internet connections are sometimes available but usually not. And if not, convincing an ISP to dig is anything but "easy".

2. Most execs have no interest in building a big office in a remote location, both for personal reasons and for legitimate business reasons (proximity to a major airport is important in a lot of businesses).

3. Chicken-and-egg: People very reasonably won't move to most small towns due to lack of quality services (schools, hospitals, and entertainment). But those services can't be established without a critical mass of people moving into town.


You reasons mostly date to the era from 1910 to 1960. The era from 1960 to 2010 matters too, and that is more about outsourcing.

The USA already subsidizes airport service for these locations. Increasing that might be worthwhile. The same goes for good internet connections and many other services. It's like the rural electrification done a century ago.

The schools are sometimes better than the urban ones. Often there are pros and cons that could be considered to even out. We can expand Teach for America if need be, but I think things are mostly fine already.


Boston, NYC, and DC are all similarly fucked. Not as bad, but not good...

Part of the problem is that a lot of wage growth is concentrated in areas that are experiencing a housing crunch.


> Part of the problem is that a lot of wage growth is concentrated in areas that are experiencing a housing crunch.

This is actually a really good point. There's actually a great paper that covers how much higher housing prices have hurt growth due to workers being discouraged from moving to high productivity areas[1]. The tl;dr is that if only NYC, SF, and San Jose adopted the land uses restrictions of a median US city, GDP would be about 9% higher (about $8,775 per worker assuming the labor share of GDP and number of workers doesn't change).

[1] http://www.nber.org/papers/w21154.pdf


> With one of the most restrictive IP licensing scheme I've encountered in my professional life. Way to promote innovation indeed.

Different business models are different, and things tend to get ugly when you find a way to print money.

I'll take the "restrictive licensing/patents" model over the Google/Facebook "private sector surveillance" model any day of the week...

> At the risk of sounding sarcastic, I have a very hard time putting SAP and innovation in the same sentence. They're basically the Oracle of Germany.

I think IBM might be a better comparison. Certainly the scale of the past century, both SAP and IBM did plenty of innovation.


> Mostly we aren't educating young children. Rather, they are the recipients of memes

Guided repetition is a common educational tool.

I guess you can call that a "meme" if you want, but that doesn't make it "not education".

> By contrast, arithmetic is intentionally and exhaustively taught, yet most adults cannot perform it.

In countries where arithmetic is taught, adults are certainly capable of performing basic arithmetic.

I have yet to meet a literate adult who couldn't compute some arbitrary sum or solve a multiplication problem. In fact, the only counter-examples I've discovered are that a lot of people have problems remembering order of operations. But that's more about language/notation than arithmetic -- if you put the parens in, they'll give you the correct answer.

> It has been speculated that if we tried to educate children how to walk and how to talk then they wouldn't succeed at either!

I was taught to talk. Some of the other children in my class were deaf, and even they eventually learned how to talk (albeit not as well as you or me). I assure you, they weren't "meme'ing". There was a lot of rather complex guiding that looks a lot like what I imagine you call "education".

>> But you cannot reset a human being.

> See Tom Scott's face around 3:30

That's... pretty weak evidence. And also a weird definition of "reset". Presumably, he still knows his name is Tom, his mother's phone number, and can write an essay or add numbers together...


>I guess you can call that a "meme" if you want, but that doesn't make it "not education".

The kind of memes I'm referring to transmit spontaneously, though no doubt intentional cultivation is beneficial in some cases. There's a technical term due to Daniel Dennett: synanthropic memes. These are extremely sticky behaviours/ideas that thrive autonomously in the presence of humans, just as some biological species do, e.g. pigeons, rats, barn swallows. Some are bad. For example, swearing, bullying and perhaps even certain motor tics are memetic and these are considered bad by many.

Our ideas about education are pretty messed up and thus we ultimately have some disturbing realities to face, quite apart from the mounting student debt :-/ Hopefully there will be a clearing up if and when we develop AGI and thus gain a better understanding of how the mind works.


When I turn my computer off and on again, I don't lose all my files.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: