hermanradtke

8 ms·

61.
by hermanradtke 3y ago
We use a weekly Google doc. I find Slack to be slightly too unstructured. Whatever the medium, I find async stand up to be very effective. We do have a stand up, but we spend almost the entire time discussing real issues. Not needed? Don’t
62.
by hermanradtke 3y ago
Without some sort of background on cost or scale it is hard to judge any of these decisions.
63.
by hermanradtke 3y ago
I worked on a system where someone did this. They didn’t consider data races so managing this system became impossible. I don’t use redux, but I also don’t think this is the way.
64.
by hermanradtke 3y ago
Is the app giving away any more data than what was being given away by using a credit card?
65.
by hermanradtke 3y ago
I believe the client is the _most_ important thing to focus on, but is often secondary to the needs of the server. True RESTful (HATEOAS) APIs are really powerful, but they are a major pain for any client to implement. GraphQL APIs are wors
66.
by hermanradtke 3y ago
The article has a whole section about the problems they ran into with two crates: https://nullderef.com/blog/rust-async-sync/#_duplicating_the...
67.
by hermanradtke 3y ago
> how many general tools cell phones replace The article says the students received phones with some of these tools: > instead coming with deliberately cumbersome versions of music and mapping apps
68.
by hermanradtke 3y ago
> the sales dynamic is very different For enterprise SaaS, QBRs and contract renewals are the point where sales shares all the new features as part of the story as to why the company should continue being a customer.
69.
Silicon Valley Runs on Futurity(davekarpf.substack.com)
2 points by hermanradtke 3y ago|0 comments
70.
by hermanradtke 3y ago
> site is still working fine Twitter has had a lot of issues and generally failing as a company at the moment.
71.
by hermanradtke 3y ago
> we keep feature branches short-lived (ideally at most 2-3 weeks) People that do trunk-based development would consider 2-3 weeks as quite long. My definition of short-lived is about 1 day.
72.
by hermanradtke 3y ago
They have a whole UI that avoids any sort of VCL.
73.
by hermanradtke 3y ago
> you could just write test cases to check for it This effectively means you are building an embedded database in your application and using the networked database for storage. There are a few reasons to do this and a million reasons not
74.
Non-Send Futures When?(matklad.github.io)
3 points by hermanradtke 3y ago|0 comments
75.
by hermanradtke 3y ago
It is worse. The sleep formula article says free sleep often involves 24 hour sleep sessions, which is practically impossible for most people.
76.
by hermanradtke 3y ago
> only when you are very tired The sleep formula article said “truly sleepy” which, to me, is significantly different from “very tired”.
77.
by hermanradtke 3y ago
Maybe prettier will consume the biome work and offer it as an option for prettier going forward.
78.
by hermanradtke 3y ago
This same thing can be applied to contracts when firing events, etc. I point people to https://engineering.linkedin.com/distributed-systems/log-wha... and use the same approach to ownership.
79.
by hermanradtke 3y ago
It reads to me that your company lacks standards and expectations to hold employees accountable. The in office culture uses the proximity of people to work around the lack of standards and expectations. If the standards did exist then bad d
80.
by hermanradtke 3y ago
> I have witnessed a dev colleague who worked from home. They were unable to document and communicate, and it screwed everyone else. How did working in an office improve the documentation abilities of this employee? > doing all the ti
81.
by hermanradtke 3y ago
> he's never actually been convicted of fraud has he? His corporation was given the death penalty for wildly overstating the value of assets.
82.
by hermanradtke 3y ago
Flagging someone as a kernel contributor should not be conflated with the magnitude of contributions.
83.
by hermanradtke 3y ago
> that huge American company powering a lot of hospital IT Epic
84.
by hermanradtke 3y ago
Now do the same with dynamic types and unit tests.
85.
Low Latency Logging in Rust(ochagavia.nl)
4 points by hermanradtke 3y ago|0 comments
86.
by hermanradtke 3y ago
Fair call out. I responded to similar feedback here: https://news.ycombinator.com/item?id=37525992
87.
by hermanradtke 3y ago
I was frustrated with my naming too. > technically correct I only ever see it used with CDNs and load balancing That is why I used it! I responded in https://news.ycombinator.com/item?id=37525971 that maybe I should chan
88.
by hermanradtke 3y ago
> to me orign would be the SENDER My history with CDNs is that origin refers to the server sitting behind the proxy. I do agree that > where the message ORIGNates from makes sense too.
89.
by hermanradtke 3y ago
> It forces the customer to focus on getting the requirements right instead of hand waving it like "oh yeah, that's just what I want" and then come back later "I didn't want that, what I meant was" repeat ad
90.
by hermanradtke 3y ago
> Would all tools then need to be updated to support it? The effort to translate JSON to another structured data format is orders of magnitude easier than converting the unstructured mess we have now into JSON. So, it does not matter if

More ›