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

> For whatever it's worth, physicists aren't necessarily up on everything written by the medical community. Take for example, ...

I'm confused. While I definitely believe that you are correct in that assessment, the example you gave doesn't seem relevant.

Mary Tai was an EDD (doctorate of education), not a physicist. and the reply was from the mathematical community, not the medical community.


1. Skill Building. I.e., the same reason we start teaching them to write letters in kindergarten even though they won't have a practical need for writing until late in elementary school. So that there's a foundation to build on later.

2. Feedback. E.g., there are some good fractions apps that help students understand what it means to "divide" a set of things into a set of groups of things. you can do that on pencil/paper or with other props, but there's no tight feedback loop.

It's unclear whether (2) is strictly a good thing; learning how to validate your own results is also an important skill...


> It's like you haven't even used it, or actually have no use case to use it for creation.

FWIW iPads and android tablets tend to not work for most software development tasks.The "iPads aren't for producers" mentality might be more of a "iPads aren't for Software producers (and some types of engineers)"


> FWIW iPads and android tablets tend to not work for most software development tasks.

It's certainly not for local Windows application development, but it's great for 21st century architectures (infra as code), containerized apps, or any other CI/CD-able scenario.

With an iPad Pro, Apple's Smart Keyboard, and the lovely Working Copy + Textastic, and blink.sh Mosh/SSH client, together with a decent CI/CD (commit code, deploy to dev) pipeline in place, you're good.

See also Buffer, GoCodeEditor, Koder, etc. Several of these happen to be 50% off atm.

Don't forget you can remote desktop to GUI things too, from Citrix to RDP.


On a conventional laptop I can run the entire stack locally.

This can be anything from "run XAMPP" to "fire up a stack of virtual machines and containers allowing you to mock up an entire data centre all on one physical box."

In contrast, an iPad is little more than an editor and/or terminal that relies on a lot of outside infrastructure to do something meaningful with what you're typing.


producer ≠ developer.

I'm a producer. I produce short film and music, amongst others.

I'm also a developer. I use xCode, Dreamweaver, and Unity to develop applications and games.

Developing - that's what computers are still for. And devs know that.

Developing on-device will come, in time. I, for one, don't have a problem with needing an extra dev machine, specifically for the purpose. I understand this represents a financial burden for some, especially considering the cost of a new MacBook. I'm fortunate enough to have had a Mac by my side since I was 14, and I'm 29 now, which means more than half my life. So for me, already a Mac user, the iOS dev ecosystem was actually a blessing. I understand, however, I am obviously an outlier in that set of data.


> producer ≠ developer.

I agree; in fact, that was my whole point :)

> Developing on-device will come, in time.

We'll see what Moore and his progenitors think. Until software is the only bottleneck, there will definitely always be lower-tier, cheaper options for the N>50% of the population that doesn't need the compute/batter life/etc. that's necessary for a mobile dev machine. My WAG is that we're still a few generations (as in people generations, not tech generations) from getting there. If we ever get there at all.


Conjecture: this is a tech-centric viewpoint.

I have quite a few lawyer and doctor friends who use tablets first (usually with a BT keyboard) and only break out the computer when they need it for some very particular reason.

If you don't need root on a beefy machine and/or Windows-specific software, then a modern tablet with a bluetooth keyboard gives you more than enough compute and all the applications you need to be productive. Often with a better UX.


It's an every-field-centric viewpoint. Every field that creates something is more efficient with a keyboard. You even just supported this point yourself.


>> usually with a BT keyboard

> is more efficient with a keyboard

...?


I don't think you are contradicting prolikewh0a's point. To rephrase their point in terms of your language, it's difficult to not be (openly) anti-social if you feel like society is anti-you.

Not impossible and not necessarily excusable. Just... difficult.


>it's difficult to not be (openly) anti-social if you feel like society is anti-you.

This is really accurate. I've really had to work on making good decisions and working on some slight anger issues during my transition after pretty much all of my family abandoned me, a lot of my friends started making fun of me publicly or just abandoned me totally. It's a significant reason why I moved across the country to Seattle -- a more open and accepting area of the USA -- to make new friends and get a job that was very open to LGBT persons. It's still tough, but the life change, surrounding myself with people who support me, really helped.


Society is very anti-me. I just wear a suit to work and pretend to be someone else. Not terribly hard.


And also don't follow up a disclosure with an offer to sell exploits to the highest bidder.

Is selling an exploit to a foreign government even 100% legal? (Serious question; that seems like the sort of thing that could get one in trouble.)


If you sold to a country with standing sanctions, that could be an issue. 0-day's can also be considered munitions in some interpretations of law, though I am not a lawyer nor a weapons dealer.


The article goes on to clarify the problem: the school district has a self-funded insurance plan.

Actionable advice: check if your employer-provided healthcare is a self-funded insurance plan or a fully insured plan. And then look up the relevant consumer protections in your state for that type of plan.

Also, in case you're wondering what the hell all those hospital administrators are dong, the answer is "shaking down your employer and screwing you over":

> In a statement, St. David’s HealthCare defended its handling of Calver’s bill and sought to blame the school district and Aetna for offering such a narrow network.

>“While we did everything right in this particular situation, the structure of the patient’s insurance plan as a narrow network product placed a large portion of the financial responsibility directly on the patient because our hospital was not in-network,” the hospital said.

> WellRithms reviewed Calver’s bill in detail at the request of Kaiser Health News and determined that a reasonable reimbursement would have been $26,985. That’s less than half what Aetna paid.


I wonder if the local county this school district is in, also provides only a "self-funded" plan to their employees. Are all the government employees getting screwed or just the teachers? It's a quaint ethical puzzle which is worse.

So the last line, "less than half what Aetna paid", does that ostensibly mean the hospital is definitely charging an unreasonable price, and by having been paid twice what is reasonable by Aetna that ostensibly this teacher shouldn't have to pay a dime? It's just a contractual reason he owes this money?


It's useful to understand what a "self-funded" plan means.

People in the US are used to their employers purchasing group health plans from insurance companies. In that model, a premium (often part paid by the employer, part by the employee) is paid to an insurance company in return for coverage. When there's a claim, the insurance company pays, out of its own money, and the insurance company's profit comes from taking in more money in premiums than it pays out in claims.

In a self-funded plan, the employer and employees still pay premiums, and all that money goes into a pool which is used to pay the claims. Typically a company is hired to administer the plan, but that company is not an insurer, and that company does not pay claims; the money to pay off claims comes directly out of that pool of premiums.

What this means is that the administrator just pays whatever it's told to pay by the company that hired them to run the plan. It's not the administrator's money being spent, and their profit is in the fees they charge to run the plan, not in denying or underpaying claims.

My very first real job out of school, years and years ago, was a place that did administration for self-funded plans. About once a month we'd get a call from one of our client companies saying "yeah, we know our plan's rules say not to pay that claim, but we want to pay that claim". And we'd say "OK, it's your plan and your money, you make the rules".

The downside is that if the company gets into financial trouble, its contributions to the pool of money that pays claims are often one of the first things to stop happening. I remember pretty clearly one client company that went bankrupt and just stopped paying into its plan, and once the money in the plan's pool ran out there were no more claims paid.


> does that ostensibly mean the hospital is definitely charging an unreasonable price

Not ostensibly, but actually.

The article goes on to identify some concrete charges that independent auditors felt were ridiculous, including charging $19k for stents that the hospital most likely purchased for about $2K.

> It's just a contractual reason he owes this money?

The hospital just straight up dropped all but $800 of the charges when they got PR heat.


> There are tons of people competing for every (faculty) job.

This is not at all the case in Computer Science. Especially permanent positions at CCs and lecturing at universities, there are more roles than people at the moment. Mostly because the worst-case alternative is taking one of the plentifully available 100k-200k industry jobs. Especially in ML.

Generally, "don't get a Ph.D. planning that you'll be a professor" is good advice. CS at the moment is the exception that proves the rule. Especially outside of R1.


>Still, I remember having to cache initialization state in PHP because it took too long to build it on every request. That's when the model breaks down and you prefer a server with state.

I also had this problem, but fortunately, I could always buy my way out of the problem better hardware and maybe one afternoon of optimization.

I finally shut down the last of my PHP side projects because of pervasive security issues and a dwindling/dead community. I recently reinstalled one of those sites on a DO droplet. Getting the right versions of everything took an entire weekend, but I eventually succeeded. The droplet had way more RAM and a faster CPU than I had access to back in the day.

But holy hell those pages still loaded so slowly. I probably didn't notice at the time because internet connections were so much slower and waiting for an HTTP page with a few images to load was normal. But those load times would be absolutely unacceptable today.


Presumably, this guy's never seen $_SESSION hell: enormous amounts of state stashed in a single super-global associative array that persists between sessions [1].

In addition to $_SESSION hell, lots of custom PHP applications end up with extremely complex and convoluted MySQL tables dedicated to storing what would typically be global application state.

Both of these can lead to difficult-to-debug performance issues, race conditions, and especially security vulnerabilities.

Global state is going to happen, so languages/libraries should provide mechanisms that make it easy to state and enforce strict invariants on reads and writes to global state.

[1] http://php.net/manual/en/reserved.variables.session.php


I don't like sessions in PHP: most times the problem can be solved without them.

But sessions are available in other languages as well:

- https://docs.djangoproject.com/en/2.1/topics/http/sessions/

- https://guides.rubyonrails.org/security.html#sessions

- https://www.npmjs.com/package/express-session


Thats pretty much a bad practice well documented accross various php tutorials and books. But many php developers have no understanding of programming so they stash everything in that _SESSION superglobal or do other scary things.


Global state in general is bad practice well documented across tutorials and books about programming. Article's argument is that PHP avoids global state, but _SESSION hell and "MySQL table as global state" patterns demonstrate that programmers will always find a way to shoot themselves in the foot with global state :)

Also, IME even good PHP programmers suffer from the "MySQL-table-as-global-runtime-state" syndrome. And it's at least as bug-prone as storing global state in an ADT.


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

Search: