code_biologist

38 ms·

481.
by code_biologist 6y ago
Have you tried to get your hands on any of the Intel HEDT parts? There's little to no supply and the supply that does exist is heavily marked up. 3950Xs and Threadrippers are in stock everywhere.
482.
by code_biologist 6y ago
It already sounds like the environment in Intel isn't great, and a lot of the staff dynamics are very driven by cost-cutting. Great video on youtube posted in the last week with a bunch of leaks from Intel employees: https:/&#x2F
483.
by code_biologist 6y ago
Can you speak briefly to the change? What motivated it? How's it been working out? For context, I'm an engineer that uses Postgres heavily, with some basic BigQuery + Redshift. I don't understand what the benefit of something
484.
by code_biologist 6y ago
They're furloughed, not laid off. I doubt they'll lose anyone who wasn't intending to leave. I get that John is down, and I definitely don't have whatever insight led him to say "even if I'm lucky enough to ret
485.
by code_biologist 7y ago
Not sure if it's quality, but I found this: https://github.com/TkTech/pysimdjson
486.
by code_biologist 7y ago
Haven't actually used simdjson, but the love and care put into the API is evident. Looks great!
487.
by code_biologist 7y ago
I love that book. If you want those thoughts in a highly condensed manner, the author Ryan Singer has done a number of interviews discussing the high level concepts of Shape Up. I particularly like the Software Engineering Radio interview:
488.
by code_biologist 7y ago
I agree with you, but I am being serious that there are developers stumbling into poor microservice architectures based on "microservices are best practice", ie. fashion.
489.
by code_biologist 7y ago
> The ultimate question though is, why are these services even separate if they're mutating the same data? Just merge the services (or at least the operation in question) instead of rewriting the entire app. Because if you did that
490.
by code_biologist 7y ago
Care to elaborate?
491.
by code_biologist 7y ago
Unshortened URL: https://news.ycombinator.com/item?id=22376468 "The Wetware Crisis: The Dead Sea Effect"
492.
by code_biologist 7y ago
I would also say that I've had "conflict between what a designer wants and what the user/business wants", which is a pain.
493.
by code_biologist 7y ago
I found this interview very frustrating to listen to. Lex keeps asking questions about magic, consciousness, AI, and all that stuff... and Jim's a chip designer. Beyond that, Jim doesn't seem very forthcoming about his thoughts on
494.
by code_biologist 7y ago
I recently built an AMD hackintosh and although I love it — this build guide is exactly what I'd do if I did it again.
495.
by code_biologist 7y ago
Chiming in as someone who experiences an inner monologue, but does not subvocalize while either thinking or reading. I don't think one implies the other. I was taught to read without subvocalizing and I think I am a faster reader for i
496.
by code_biologist 7y ago
Yeah. Coming from a Django world it's about avoiding surprises for application programmers. I suspect it's the same in Rails. Historically Django has almost entirely had logic at the application level rather than pushing it into t
497.
by code_biologist 7y ago
Presumably if you're materializing a view, you have to have a cache for speed — it's either this or ElasticSearch or Redis. For me, where possible, it's nice to have a correct cache a `REFRESH MATERIALIZED VIEW` away instead
498.
by code_biologist 7y ago
Overall, I love this approach, but the big pain for me is the lack of incremental view refreshes. I end up needing to recreate giant tables each refresh even though the underlying changes are small. Sure I could implement that myself, but t
499.
by code_biologist 7y ago
This is exactly the sort of encoding issues that the python 2 to 3 transition has flushed out. People get frustrated with python 3, yet the actual failure was their mishandling of encoding issues -- papered over by python 2.
500.
by code_biologist 7y ago
What solution do you use for async Redux code?
501.
by code_biologist 7y ago
If we're being pedants, "Dennard scaling" is the term for the phenomena that allowed for increased clocks: https://en.wikipedia.org/wiki/Dennard_scaling Dennard scaling was a nice side benefit of transis
502.
by code_biologist 7y ago
I think his take on databases is moronic with a dash of common sense: He rails against a strawman where people put SQL everywhere, into views, into application logic ("mail merge" is one he mentions), and DBAs gatekeep everything.
503.
by code_biologist 7y ago
I think it's reasonable to ask with respect to HN policy. It's hard to have a meaningful discussion when only a small percentage of the people on HN can read the full article. What percentage of HN visitors do you think can read t
504.
by code_biologist 7y ago
Great article. This hits close to home as a product developer. I'm certain this phenomena happens in "data driven" product decisions. Top of the funnel, we have the numbers to get statistically sound outcomes on A/B test
505.
by code_biologist 7y ago
Data modelling. The data model pervades any given piece of software, so it's hard to change. If there are mistakes in it, you will see workarounds all throughout a codebase.
506.
by code_biologist 7y ago
If you're into adhesives, the Applied Science (Ben Krasnow) youtube channel has a great video discussing his shortlist of adhesives to keep around and when/how to use them. "Tools and Tips #1 from Applied Science": http
507.
by code_biologist 7y ago
That approach is sound, but challenging, IMHO. The two major issues you run into are "how do we allocate resources between the boutique and the off-the-shelf version?" and "how do we manage the functional differences between
508.
by code_biologist 7y ago
Catabolism is another aspect of thinking about code as an organic entity that I find useful. Anabolic (growth) processes and catabolic (teardown) processes always accompany each other in biological systems. Too often we neglect to continual