skysight-inc/HackerNews huggingface dataset:
The degree question is interesting but in retrospect it really leads to all these false dichotomies and imagined careers. It really barely matters for a lot of people past their first job. Of course if you talk to people who love their own camp, they may want to argue.

Work-life balance will always be more about your personal ability to set boundaries with other people, and find the boundaries you need. The needed boundaries will usually differ somewhat per job, per team, per project, etc.

In general, you can have an amazing work-life balance with any degree and just about any career field, if you are planning to be intentional about this aspect, which you clearly are.

However this does mean being able to say "no" to people in various ways and in various situations. It may be downright awkward sometimes. Others may try to make you feel awkward about it, especially if they suck at setting boundaries.

If you are like me, you'll probably have to quit some jobs so you can preserve your boundaries. It's hard to say what can happen at work when you don't have all the info going into the job (you never do), or when there's a leadership change, and so on.

There are so many different approaches when it's time to act directly, too. The informational "I won't be doing that," the relational "I hear you but...," the logical "If X and Y are true, then it doesn't make sense for me to..." and the equity-seeking "since I did everything you asked of me..."

It all ends with you pushing back, ideally gently but definitely persistently. Some of it will not be received well even if worded perfectly.

I had a lot of friends move from CS to MIS back in the day, and they were mostly just sick of plodding linear progress and deep puzzles (I believe we had a unique department staffing situation in that way, psychologically) and ready to keep it breezy and cheesy. They wanted more of a survey that highlighted the parts they liked best. They wanted to be excited about computer stuff in general, wrap some fun team projects, learn a bunch of PM and accounting overlap skills which might come in handy, know the latest apps and dev tools for this or that, and so on. They all said they loved their new lives away from CS.

But other CS friends did just fine in their own ways.

To me the question also surfaces your willingness to trust in your future self to have the energy and strength to solve such problems as they arise. Strong contingency planners in these cases can end up trying to out-plan themselves sometimes.

Contingency planning can't bear the burden of developing your life into what you want or don't want, all by itself. So, please be sure to leave a note for future self: "Here's what I'm going for, based on limited information about what it means for you in the future. I trust you, and your problem-solving skills, with the rest." And boom, execute and move on.

This exercise may help you on the job as well, when faced with similar dichotomies. Planning and execution will mean vastly different things to some teams, but the latter is by far the most important in most jobs. For better or worse.

Good luck with whatever you decide.
It's pretty easy to browse through the writings and find their shared writings, but I don't have an index to boylove dot org or whatever nor do I want to search for it again.
The site seems to have been hugged to death, so in the mean time this article may be of interest to you:

https://www.openculture.com/2017/06/hunter-s-thompson-typed-...

Hunter S. Thompson Typed Out The Great Gatsby & A Farewell to Arms Word for Word: A Method for Learning How to Write Like the Masters
According to Krashen's language acquisition models only input matters, and typing is a very ineffective mode of reading.
Here you go:

https://timesmachine.nytimes.com/timesmachine/1906/06/05/101...

If you want to cite the report, that's great. Citing a novel with no references, nope. People can be educated just fine using facts instead of novels.

Rarely noted is TR commissioned two reports, because he didn't like the first one. The NR report was the second. I've never been able to find what the first one said.
IDK about "horrible" but https://www.sentencingproject.org/research/ puts it at 1.5 million peak. Thats not quite 1 percent of the US population but its also not that far off. And we can quibble about US sentencing rules but the BoP has a count[1] of felony categories and drugs make up less than half, and its even less in state prisons.

The reason the estimate feels high is likely that the HN crowd is progressively separated from less stable elements of society. The bullies picking on kids at recess don't generally make it onto the gifted / accelerated track, or your 4 year degree granting university. You're going to encounter fewer of them at upmarket shopping centers and corporate offices, if for no other reason, 1.5 million people are in prison.

[1]: https://www.bop.gov/about/statistics/statistics_inmate_offen...
Thank you :) Calling the police would be ideal, but then you have to involve an alarm company and use their system. They are expensive, and I wanted to build something myself.

1. Hm, maybe. If they were to arrive, they would have to call me — I could remotely disarm the system or give them the code.

2. Not sure, my closest neighbors are aware of the alarm system. No false alarms in 13 months I've been using the system.

3. I used to work as an alarm technician; you can't really prevent the pros breaking in, getting what they came for and getting out. But you can prevent someone spending a long time inside the house looking for things to steal.
Perhaps I’m a bit slow.

But there seems to be a lot of “time in lieu”, work extra take the time off.

But that’s only a 1 to 1 ratio, not 1.5 or 2.0, and.
I liked this article because it showed that ML classification is not magic, but a series of design choices from a well known (to the author) design space. And yet, he found surprising things about the emergent behavior of the classifiers even in this restricted domain.
> It is literally stupid work (pure waste) to require them to repeatedly suit-up in and later remove PPE in order to be able to do a different task.

And I never said otherwise. I am responding to your non-sequitur with the like.
I prefer System76, because it ensures that hardware and software work together flawlessly. Most threads here seem to complain about that, but I never had an issue on that front with my Oryx Pro.

Only hardware complaints are that it can become noisy with (Nvidia!) GPU use and that the battery life is short (at least if you are used to MBPs…) But for example, I have had no serious headache with the Nvidia GPU, only some driver update juggling.
You've been able to write PureScript that compiles to Erlang and has perfect interop for years, via `purerl`[0]. Using it with Elixir is as simple as adding `purerlex` as a compiler and having your PureScript code automatically compile when `mix` compiles things, and off you go.

In terms of the typing itself, it's exactly what you get in all of PureScript, strict static typing with no `any` or the like. Using `Pinto`, the de facto OTP layer in PureScript your processes are typed, i.e. their `info` messages & state are typed, which means that they are all much more like strongly typed state machines than anything else.

You can see an example of a basic `gen_server` here:

https://pastebin.com/UTEfz7Wg

The differences aren't very big in terms of what you'd expect to be doing. One small thing to note is that the `GenServer.call` expects a closure to be passed instead of having the split between `gen_server:call` & `handle_call`, removing the need for synchronizing two places for your messages being sent and handled.

0 - https://github.com/purerl/purerl

Edit:

As an upside you also have PureScript for your frontend, so you can just write everything in the same language regardless of how much frontend work you expect to be doing. PureScript has great bindings and a great story around React (it actually fits better since it's a purely functional language, so things like "You can only do effects in `useEffect`" actually are enforced and make sense) and also has its own frontend framework in Halogen which is very nice.
The goal isn’t to see how close you can get to the correct answer, it’s to see the extent to which you’re able to break down a complex problem you haven’t seen before into steps you can take to solve it.
Or someone will just resubmit this and say it was generated by chatgpt and it'll spark many hundreds of comments and rust jokes.
https://www.castingcall.club/

I'm an indie entrepreneur, so it's just me on this project, but it's been great fun.
This is a game. Should you want a digital logic simulator that's not a game, check out https://github.com/hneemann/Digital.
Agreed, I have no outdoor sensors — but will be installing an outdoor siren. It is delayed by one third of the trigger time, so with 60 seconds trigger time — the outdoor siren is delayed by 20 seconds.

Should we set off the alarm by accident, we then have 20 seconds to fix it, before all the neighbors are alerted.
If materialized view doesn't refresh data on insert/update, this basically works similar to a cache.

Caching the front page, server side, instead of rendering it on every request would have given similar result -- my guess. Specially when the query was taking 900ms.
If you have a teenager at home, make him read the story « Tibaldo and the Hole in the Calendar » about this event

https://www.amazon.com/Tibaldo-Hole-Calendar-Abner-Shimony/d...
It’s not using doc-comments, but compile-time reflection — it’s just that Rust‘s only reflection output is JSON. That doesn’t render the preposition of using a reflection API for transpiration invalid however.

As long as the output code can be verified by tests, I don’t see how this would fail in „creative ways“.
Good organization and code search is half of productivity.
It is always better to find you already have something coded then code it again.
Note to future self: stick to .com
cf EWD1293: https://www.cs.utexas.edu/users/EWD/ewd12xx/EWD1293.PDF

(note that binary search is an example of computer scientists acknowledging the existence of practitioners: they won't go so far as to do a k-ary search, for that would require engineering a [necessarily ephemeral] suitable value of k, but they have demonstrated goodwill in stepping beyond the much-cheaper-to-prove 1-ary search.)
I would have guessed they were in a station made of grey goo expanding as they went further.

But some bugs in the software (or it being incomplete/a testing version) prevented the generation of some rooms (like the bedrooms) as well as the orientation markers.
> let other people pursue their epistemologies without devaluing them?

I object to people citing fictions as fact. I've enjoyed reading historical novels, and enjoy watching historical movies. But when I know something about the history behind them, it's often clear that the facts are distorted, sometimes egregiously, to suit the creator's agenda or to make it more entertaining.

> you do not personally know how to challenge it and how to divine truth from it

That's rather presumptious, don't you think?
That's exactly what this tests for.

I have no idea what those values are! I am still able to make guesses to show that I can figure out a bunch of variables that affect the final value. And since I am multiplying data that's off maybe even by few orders of magnitude, errors multiply as well: I am aware of how erroneous input data affects the results too.

Is it relevant to software development as a whole? It definitely is.

You've got to provision web workers for new service being developed: you can only (guess)timate number of expected users, you can guess how much CPU time each request will take, figure out cost per unit, look at bandwidth requirements, and make your pick. To improve on your guess, you actually go and measure request times (p50, p99), decide on the number of users you can sustain with your team cost effectively, measure network usage, etc.

Or you need to decide on what type of DB to use? Depending on access patterns (read heavy, write heavy, time series...), data size and scalability demands, team familiarity with different tech, you make a guess at what should work: you can only measure after you've got the system exposed to real, live load.

Now, I still think it's a bad interview question: people can be perfectly comfortable answering above questions, yet not see that they are in abstract exactly the same as the number of piano tuners in NYC. It tests for that generic and general ability to estimate anything, and to break down any problem.

Yet some people get flabbergasted (like you seem to do?), since they think too much about specifics of each of the numbers they use and how wrong they might be. Basically, they have a hard time of letting go of the inaccurracies :)

As such, it's a mixture of tests: supposedly only tests you problem breakdown skills, but in reality tests your confidence in using inaccurrate numbers or lack of problem domain knowledge to solve a problem.

Which makes it a bad interview question unless both of those is what you want to learn about someone.
Ray Tracer Construction Kit
It’s called SwiftUI?
> is to small to appear

> and whoses destination is

Uh, does the author make these kind of grammatical mistakes in The Enormous Space too?
ᚒᚒᚓ ᚅᚓᚓᚇ ᚋᚑᚏᚓ ᚈᚓᚎᚈ ᚔᚅ ᚑᚌᚆᚐᚋ
If you were already going to get what you didn't vote for, what's the difference?
Well, for one thing, there are countless software systems worked on by hundreds of thousands of developers which will never include a data lake or any ETL more complex than "a programmer writes a script to generate a CSV and upload it/email it somewhere".
Wow! This is such a thorough post!

I slapped together similar (but much less impressive) take on this theme very recently. I use VNC for remote access rather than SSH'ing into my home network directly. Do you opt to just forward a port on your router and send it to your pi's SSH port? I wasn't sure how risky that would be or what options exist for that.

Also I noticed you mentioned a water sensor at the end, I did a similar project for that as well after I had some basement water issues. I just got a couple of super cheap humidity sensors and had them take a picture of the scene and email it to me if the sensors thought they were submerged. Great minds think alike! :)

https://jeskin.net/blog/raspberry-cam-home-monitoring/
> will evoke specific concepts in the people I work with

So you're aware the FOSS developers are not suppliers but feel comfortable to explain it to management in a way that clearly makes them responsible so they're able to understand what exactly? That their developers outsourced the hard to implement libraries to unpaid volunteers and only handle the mostly trivial business logic?

The term was most definitely coined to offload responsibility in big enterprise. The uncomfortable reality is that productivity would take a nosedive without using these FOSS libraries/tools, but nobody wants to admit that this comes with risks (even though they're way smaller then implementing it yourself, probably). I'd agree that it's a complicated issue, but maybe using terms management is comfortable with isn't a good idea either if their meaning didn't actually apply at all.
I cited the actual report, not a description of it, in this thread. You're welcome!
Imitating native components is actually the only realistic approach. Those components are guaranteed to work on newer OS versions, they work on any platform and they give you easy access to the low level guts.
Or, in the real world, funerary cannibalism.
Well the word was invented in the 18/1900s, along with "judeo-Christian"

Google N-Gram Viewer is fascinating for looking up how widely published certain topics/words were and when
Is there a record of people going adventurous sea explorations and not coming back?

With no acclaim there are few stories. There’s Mansa Musa’s father who crossed the Atlantic from Africa.

https://en.wikipedia.org/wiki/Mansa_Muhammad

For some reason the failures ground the triumphs.

Of exploration that is, the Spanish Conquest of the America’s being grim.
> That’s your interpretation.

It’s a well-documented fact.

> The Kennedy administration’s race is an actual, specific race with a specific plan.

The Kennedy strategy only makes sense as an a strategy within the well-documented arms race that was already occurring.

> It was a specific decision taken with specific goals in mind.

An arms race is not defined by the existence of a strategy of one side, it is an escalating cycle of response between two (or more) sides. The Kennedy strategy might help explain why the superpowers didn’t break out of the race sooner (though, really, arms races continuing until either one or both sides reach economic exhaustion or a geopolitical realignment through either war between them or intervention of a third power renders the race moot is fairly normal, so it’s plausible that the adoption of an obvious strategy by the more economically powerful power given an existing arms race did nothing.)

> I recommend watching some relevant Chomsky lectures on the matter.

There are things Chomsky might be able to convince me of, but effects preceding their causes isn’t among them.
Ask HN: Any advice on becoming more organized?
> I wrote:

You wrote that in a later example, after several simpler examples not including error handling either, and not introducing error handling at all. In fact error handling is not covered anywhere by the introductory text.

The part which really grates is that this makes all the examples in the "motivation" section for linear types work against their very section: because all the destructors are infaillible, they're perfect motivations for an affine type system and implicit destructors, all they say is that a linear type system requires more work from the user for no visible value.
> I object to people citing fictions as fact.

I would too, I don't see anyone defending the quote you highlighted though. (Though perhaps they'll show up in time, hadn't been very long).

It's no more presumptuous than saying novels can't be learned from. It was meant in good faith; take as much or as little from it as you care to, and if it bothered you, I apologize.
We (the US) love to blame the victims. Full stop.

I do support the idea that someone accused of a crime needs to be proven guilty beyond the shadow of a doubt. The nature of these crimes often results in a he said/she said scenario where the crime can't be easily proven. Only in these scenarios where the dam breaks and dozens of accusers come forth do these predators receive justice.
More importantly, not voting sends a message. A very important message. When no one votes (as is the case in Russia), it makes it clear to everyone that everyone else thinks that the system is corrupt. The government can still say "99% of people voted! WOohoo! Democracy!" but everyone knows that it's fake, because nobody they know voted. That's why some of the most corrupt countries on earth have mandatory voting.
> The reason why healthcare is expensive is because of regulatory gatekeeping which prevents new players from outcompeting incumbents

Look. In ENTIRE world except the US, that is not happening. There are far more regulations everywhere else. They also regulate prices. They work. Looking at the situation, only one of the below possibilities can be true at any given time:

1 - The US exists in a totally different space/time continuum in which what you say is true
2 - The US exists in the same continuum with the rest of the planet, and you people are being totally scammed
PlanOnDemand
not so. you can build complex apps with the expo libs.

The reason people "eject" is primarily to add 3rd party native modules for functionality not available in expokit, or to optimize build size by removing unused expokit functionality. This isnt neccessary in the vast majority of cases as you can use Expo App Services to do this (locally, or remotely if you dont have mobile sdks installed)

And you still get the other benefits of expo - e.g. "batteries included" api, OTA app updates, not having to install the mobile SDKs, etc.
Juxtaposed with the modern RasPi and Arduino, is bits of old-school: generic breadboard, through-the-hole soldering of rows of resistors, socketed DIPs...

It's great that random hobbyists can send out to have a one-off fabrication of a slick PCB. But it's also nice when we can DIY more things.
Just was in the National Irish Museum - Archeology yesterday and saw these stones for myself! These are such impressive structures, at least 5 feet high with writing so deeply engraved it’s still legible today (a specialist’s eye is still required).
As the founder of OpenFaaS, the author doesn't know how true this rings - given all the myriad enterprise users of the community edition/OSS code. Even with smaller projects like K3sup, where I've seen defence contractors have k3sup references in their codebases and issue comments, go on to ask for changes, yet publicly stating they've never used it.

We did pivot the business model in ~ 2019 to open core, and I've tried to apply that to future endeavours like inlets, with the latest "actuated" - self-hosted CI in microVMs - it's a SaaS, with no open source components.

The common retort from users is "when we're in production, we'll pay for support / sponsor the project" - this literally never happens.

I applaud the author for laying it out how it is - there is no business relationship, open source maintainers are not suppliers, but if you want us to become your suppliers, have procurement reach out. Because we may well be able to offer you a relationship that would be mutually beneficial.
> 4. Year of Linux desktop!

Steam Deck is the best gaming console that I've owned.
> Realistically, it shouldn't, and there's no way you would be able to handle it properly even if it did.

So you think it is better to continue execution completely oblivious of the issue? Or do you assume `close` will straight up terminate the program if it fails?

> Flush your FDs to ensure you get write errors before closing.

Nothing precludes implementing `closeFile` by flushing it, returning any error as a failure, then actually closing.
> I haven’t worried much about my typing speed in years (100WPM is faster than I can think when coding or writing most of the time),

I hear this argument all the time and I don't buy it. Yes, my thinking is slower than 100 wpm on average, but it is extremely bursty. It goes at 0 wpm most of the time then 10000 wpm for short intervals.

I believe the fundamental concern here is not average speed, but latency. How fast can you get the current thought onto the page so that your brain can move on to think about the next thing?

I also type at 100 wpm, and I find my wetware CPU experiences stalled cycles while I'm typing, not able to continue because it needs to hold on to a buffer containing the thought I'm slowly typing out.