lastofus

Isn't partaking in thought-provoking discussion reward enough?

This also seems like one of those things where Goodhart's law may apply.

Even if there were no free alternatives to Oracle's JDK (there are plenty), who looks at the cost of engineering time, opportunity costs, and thinks "yeah, this is way cheaper than paying Oracle"?

Assuming your product is live, you should have hard analytic data to support your decision making one way or the other. If you don't have browser stats, your first step is installing google analytics or a similar offering (or just crawling your server logs).

If you are serious about saturating your pipe as a business with some cash to spend, there is Aspera. My understanding is that they build their own protocol on top of UDP to avoid pesky behavior of TCP.

Don't write off non-profits and NGOs. Working at an NGO is probably the most content I've been career wise, even if the technical problems being solved are not the most challenging.

The people there are amazing, and being in an environment where people are not just trying to help the company earn more dollars is like a weight off my soul.

I found this comment enlightening: https://clojuredocs.org/clojure.core/send-off#example-593472...

It seems like there are a lot of parallels between agents and core.async.

Agents, like go blocks, run in a thread pool. Any blocking IO should be pushed off to a separate thread outside of the thread pool. In the case of agents, there is (send-off). In the case of core.async, there is (thread)

I believe all I/O is blocking unless you use something that wraps NIO. This is definitely true for core.async threads, but I'm not sure why it would any different for agents.

This is also a bit of a departure for people coming from Go or Erlang/Elixir.

My 2 year old is just happy to talk on the computer mouse like it's a phone.

Not sure where I would start other than "daddy reading".

Number 6 is basically the Secret app, though the community quality there isn’t great.

Also, googling "github for recipes" brings up a number of options as well.

Out of curiosity, what kind of apps do you work on day to day?

> If there are 50 commits in every release, and a 2% chance of a given commit breaking something, then in expectation every monolith deploy gets rolled back.

> Microservices are one way out of that cycle.

Is the implication that microservices lead to fewer bugs, or that microservices allow you to roll back one service instead of the monolith app as a whole?

I would argue the former implication is a dubious claim, and the later doesn't make sense if other services depend on a given service running the latest version, which is often the case when implementing new features.

If you are releasing bugs with every rollout that require a rollback, then perhaps a simpler solution is to do smaller releases with an improved testing/QA cycle.

Learning and customizing someone else's boilerplate can be just as time consuming, though you will probably learn a thing or two in the process.

If you really want to understand the fundamentals, look into writing a toy HTTP server from scratching starting with sockets. The language you choose to do this in doesn't matter quite as much, but bonus points if you use C and the POSIX API directly.

Once you have accepted a connection, you then have to decide how to handle multiple concurrent connections. Do you use threads? Sub-processes? select/poll?

You can then move on to reading/writing to shared state. Do you use memory? Files on disk? A SQL DB? If using threads/processes, is concurrent access to those resources done safely?

It's a long journey to do the above well. I highly recommend anything/everything by W. Richard Stevens https://en.wikipedia.org/wiki/W._Richard_Stevens

I believe it was in Eskepa's "The Cure for Alcoholism"

I'm in the same boat regarding interruptions. A lock on the door can help.

It depends, as both front-end and back-end have large ranges of complexity. In general though, if you were to compare the most extreme case of back-end complexity to the most extreme case of front-end complexity, the back-end case would be more difficult.

The worst case of back-end complexity requires very in-depth knowledge of hardware, networking, distributed computing, OS internals, and then knowledge of a couple of languages and CS fundamentals thrown on top.

The worst case of front-end complexity requires learning and writing tooling to make writing desktop replacement apps in a browser a less terrible experience. Tack on UI/UX design, you are still not quite at the same level of complexity.

I don't mean to say that front-end isn't difficult or that it doesn't take years to master, just that back-end is even worse...

HAML for HTML is still around.

SASS is nice for CSS.

ClojureScript + Reagent/Re-frame is amazing though! (See Hiccup syntax)

Perhaps offer cloud based backups/syncing of notes across devices. You could use git to track history of changes over time on the server. Charge a monthly fee for this feature to cover hosting + profit.

I believe I read that Dr. Sinclair was thinking Naltrexone could also be used to help with any sort of addiction such as smoking or overeating. I don't think there is any clinical research to support this though in the same way there is research supporting its effectiveness with alcoholism.

Related: "Perfect is the enemy of good"

And in the case of side projects: "Best practices are the enemy of fun"

The followup argument is usually something along the lines of quantum mechanics is just probabilistic as far as we know.

Quantum physics doesn't allow for free will in an otherwise deterministic universe, any more than hooking up a RNG to a computer allows for the computer to have free will.

Just logging out on all devices has been enough to break the reflex for me. Typing in my email and password, especially on mobile, is enough to prevent me from proceeding.

> I would really love to know why this was downvoted?

Some bar napkin math:

$150k (savings) + $40k (living expenses) = $190k post tax.

Assuming 30% goes to taxes (making liberal use of a 401k), that would be $272k salary. @ 35% it would be $292k.

I think the reason everyone is annoyed/down voting is the assumption that every developer in the bay area is pulling top end salaries like that. The reality is the median dev salary is a lot closer to $140k/yr. It's also quite difficult to live on $40k/yr for most people in the bay area ($3.3k/mo). It's definitely possible but compromises will be made (e.g. no children, live with partner/roommates, have no expensive hobbies, no travel, etc).

Assuming everyone is as fortunate as you, and is willing to make the same compromises as you can come off as condescending, as if everyone is is screwing up and they just need to do this simple easy thing you are doing. It's akin to "why don't you poor people just earn more money??"

With that said, congrats on kicking ass at the savings game, and I hope you enjoy your early retirement :)

I regret that I will have RSI pain in my arms for the rest of my life. Chronic pain is depressing.

They are probably referring to not being an accredited investor.

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

I've personally experienced this with a YC backed company that still posts job listings on here.

After 2 full days on-site with said company, I got radio silence. Not even a quick "thanks but no" email.

It was much nicer than Perl in that I could actually read and understand code I wrote 6+ months back.

If you have passable people skills and enjoy a bit of travel, you may consider sales engineering.

You basically handle all of the technical things that are over the heads of the normal sales team, both pre and post sales. This will often look like integration type work -- trying to figure out how to make your companies product work in the prospect/customer's environment.

The editor based REPL is how the Clojure folks stay productive (as opposed to running tests at the command line). Using a keyboard shortcut to eval any expression in your code is really great.

The stacktraces are still often terrible though =/

If you ever decide you want to cutback/stop with the alcohol, I highly recommend the Sinclair Method.