rmdashrfstar

Can I create profile data by running the instrumented binaries through testcases? Perhaps integration test cases which represent typical end to end functionality of my application.

What could they be doing with all those redirects?

I'm not sure calling the domain layer "anemic" by default is correct, as it's typically a (negative) descriptions of models which are too data-driven instead of behavior-driven. I would suggest an alternative layer structure: Initiators/Controllers -> Application/Domain/Infrastructure Services -> Domain Models/Business Rules/Invariant Checking

While Given When Then rolls off the tongue easier, I think Arrange Act Assert better describes the structure

Can you clarify what subcontinental Indian English will supposedly do to en-us?

Thanks for taking the time to write all of this out!

You are awesome!

What’s not “boring” about developing a backend in Rust? Rust is one of the most boring languages I can think of.

I, for one, love Safari! I will use Safari on MacOS and Firefox on Linux, but only Chrome for frontend development and testing...

Yes, there are many things worth discussing which would be better left not written down.

> “I’m just at peace with the possibility of something bad happening to me.”

I think this is the key thing to understand, as well as not worrying about things which are outside of your own control. If your own personal actions did not or will not be a factor in the outcome of something, whatever that something is, then it is pointless to worry or fret about it. Be concerned and happy about what is in your control!

Or just stop drinking alcohol and soda, that’s another way to solve this dilemma

Gotta love all the HN armchair gatekeepers in this thread

It’s simply unbelievable!

“For those of you who want a TL:DR summary, here it is: It’s time to get back to the work marketers used to be really good at: Deciding on the appropriate context in which to engage your audience. And it’s time to pull back from a habit most of you have fallen into: Letting the machines choose your audience for you. Thanks to new approaches which fuse at-scale ad targeting with high-quality editorial product, you can step into this renewed role without sacrificing the reach, precision, and targeting afforded by the likes of Facebook, Google, Twitter, and their kin.”

Are you sure you’re building anything foundational if you need to be drinking for it to occur?

I’m just waiting to read “This research was funded in part by the Molson Coors Brewing Company”.

Ask HN: Should I start drinking regularly?

Alternatively, if you’re looking to create a web application but only expose it through an HTTP API, you can simply choose an HTTP router like Routerify [1] to route HTTP requests to a stateful handler and any number of middlewares. I’m coming from Go and learning backend web dev in Rust, and this crate has been a wonderful replacement for the Go library “Chi” [2].

This comes in handy when your frontend is a SPA (e.g. Vue, React) and it’s just updating state via API calls

[1] https://github.com/routerify/routerify [2] https://github.com/go-chi/chi

That’s why you write unit and integration tests :) That’s how you get a fast feedback loop, instead of looking for it in compilation

Use sccache and an S3 bucket

"For me and not for thee"

Thanks for posting this, reading about all the progress made with delay tolerant networking is exciting!

Do you have any recommendations for where to learn more about network eng for us non-network-engs? My experience is in DevOps (on k8s, mostly) and systems/application programming, if that helps pinpoint any advice you could give. I’m trying to get the bigger picture like network engineers understand, as well as start to understand the layer 2 topology that you described.

My tech stack: Rust, Redis, MongoDB, is most loved on Stack Overflow, and most hated on HN! That must be a good sign. :)

Rust is a complete breakthrough in modern popular languages as a safe, fast, and expressive alternative.

MongoDB, or really any aggregate-oriented database, is perfect when you’re modeling your domain as aggregates and you align your data access patterns with the design of these aggregates. Do your homework to set the right settings, take regular backups, then focus on what matters (hint: it’s not really persistence).

Redis is a no-brainer, it’s just plain great for managing user sessions.

There’s a place for everything, keep your mind open :) https://martinfowler.com/bliki/PolyglotPersistence.html

The main argument for using MongoDB when you’re abiding by DDD: https://martinfowler.com/bliki/AggregateOrientedDatabase.htm...

Main argument for using document-oriented databases: https://martinfowler.com/bliki/AggregateOrientedDatabase.htm...

The main argument for using a documented-oriented database: https://martinfowler.com/bliki/AggregateOrientedDatabase.htm...

Interesting taste of my own medicine. Will do, thanks for the reminder!

I wouldn’t say DevOps does not include “building stuff”, but you’re building certain kinds of stuff, like systems to manage CI/CD for projects, deployment environments, promotion of versions, releases, security scans, collecting KPIs on CI/CD (which provide management with more accurate visibility onto the velocity of a project), etc.

Sure, you’re not writing the application, but you’re doing a ton for the work around it to make sure it runs.

The institutions are all humans, I think it’s an “us” problem :)