chrsig

No, it's really a terrible thing -- both for what you noted, and the fact that if a relationship sours it could impact coworkers.

Any given relationship sprouting from coworking isn't terrible, but in aggregate, I think it warrants a decent amount of frowning.

> LLMs hallucinate, and there is absolutely no space for hallucination in a court of law.

Well, _someone_ doesn't have enough schizophrenia in their life.

Yeah, I'd be really curious how it fairs on jespen now. Back then it did...poorly

https://aphyr.com/posts/323-jepsen-elasticsearch-1-5-0

It definitely seems like it's gotten more robust since the 0.9.x/1.x/2.x days. And a lot of stuff that had to be done externally is starting to be baked into the service itself (rolling over indices, rolling up based on a query)

I'm a bit cautious using 8.x, because opensearch forked at 7.x. I don't really have any desire to keep track of any divergences between the two :-/ It's really unfortunate that there's so much bad blood between elastic and aws.

1. That presumes linking against libmysql and making bindings won't be a source of endless bugs :)

2. One of the major pitfalls with linking against c libraries that do their own i/o is that they don't play nicely with the go scheduler. That means the goroutines blocking on a c i/o operation will occupy it's thread for the duration of the call.

> First, it’s really easy to ignore the beta docs and end up learning class components. She wasn’t happy when I explained to her that what she had just learned is pretty out of date and not at all what the ecosystem uses.

Yeah, that's an absolutely terrible experience.

Why can't there be a modicum of stability in the ecosystem?

...what is the agenda being pushed here?

it's quite a wordy title!

"internalizing problems" seems like it's notably different than "mental health issues"

It's a major component of ADHD. Not the only component. It is probably the most detrimental component to life stability though. I think it's fair to put it in the spotlight.

Get me in a whiteboard session, and you get responses that I've spent 15 seconds tops thinking about. Send me an email and you'll get responses that I've spent an hour or two thinking about.

There'll also be a written record of the exchange for future reference. The time spent writing the email isn't wasted. It's time saved putting together documentation.

I've looked at mermaid & planetuml before. structurizr is new to me and looks interesting.

PlanetUML has the advantage of gitlab support, iirc -- allowing rendering of diagrams in README files. I'd like to see more options for that.

edit: interestingly, the author of structurizr (Simon Brown) was recently linked in another HN thread.

HN thread - https://news.ycombinator.com/item?id=34338995

YT link - https://www.youtube.com/watch?v=x2-rSnhpw0g

I haven't looked at the implementation at all, but it is possible that the pool is keeping goroutines alive, and the `Go()` method writes to a single `chan func()` that those goroutines read off of.

Which still isn't exactly equivalent, there's still an additional channel read due to the `for elem := range stream {}` loop, and likely an allocation due to the closure.

...are "the city is burning down" and "everything is fine" the only states you think of?

"Overstated" doesn't mean everything's fine, it means that it wasn't as bad as they made it out to be.

>I'm old-school, and even I rarely use unfiltered strace anymore. Too noisy on a complex/concurrent program, and not just because of dumb stuff. I filter it down to what I'm looking for or use another tool entirely.

This!

Learning all of the strace flags is a very useful endeavor. Filtering is a must to see exactly the calls that I'm looking for.

I don't think most developers appreciate how often syscalls happen. Without filtering, you're getting all:

- file i/o (read, write, readv, writev, pread, pwrite, ...)

- network i/o (select, poll, accept, epoll, ...)

- memory allocations (mmap,munmap, sbrk, ...)

- process querying (getenv/setenv, getpid, gettid,...)

- time (gettimeofday, sleep, ...)

- synchronization (futex, ...)

I'm sure there's a bunch more that I'm neglecting. It produces quite a bit of noise!

I'm electing not to. I don't want to put any one specific persons behavior under a microscope publicly. There are specific examples that I'm thinking of, but linking to a video of them attaches a face, voice, name, etc.

I'd hate to put myself out there doing a talk and be on the receiving end of that sort of indirect criticism. It wouldn't be feedback to the person, it'd just be something for us to argue about whether they're exhibiting a given behavior or not.

Debate has its place, that doesn't mean everything needs to be debated at all points in time, or that people shouldn't just accept that they disagree on something and move on.

> If instead the culture had focused on the more subjective aspects of language choice, I think we would be a lot better off.

Maybe? Who's to say what would have happened in some alternate timeline. There's no way to get an actual answer, so there's not much value beyond entertainment in discussion. Perhaps the exercise might provoke thought.

ehhh, I think if you watch the cppcon videos, you can get a taste of what the OP is talking about.

The cpp community is possibly the worst offender on some of the points. Speakers walking on eggshells and having to have a laundry list of caveats comes to mind.

It's more mature in the sense that you probably wont see a lot of memes, the insecurity and ego still permeate the venue and community.

Yes. It can be truly exhausting, for all the reasons noted.

There's a flip side to providing caveats and walking on egg shells: The culture is terrible at providing feedback. It's given when not requested, it's usually very very pedantic, or possibly delivered with some degree of irritation.

One thing that I find helps: separate things into objective and subjective categories.

code quality, best language, good design, cleanliness -- examples of subjective measures. They're going to vary by person, background and experience, thought processes, etc. They make for entertaining discussion topics, but not usually productive ones.

These generally are also the areas where people's egos and self worth get wrapped up. No one wants to feel like they're producing unclean code.

I try to focus more on objective things: does it produce the correct result? how much time will it take to on board someone to x y or z? It usually helps keep the discussion productive and helps keep egos at bay.

It's difficult though. People have opinions, and they want you to know about them. and they want those opinions to be facts. And it's most likely something we're all guilty of.

I'm curious if any HNers have opinions on prometheus vs other time series databases like influxdb?

I periodically consider a grafana & backend setup for when datadog becomes cost prohibitive for metrics with several tags.

nah, compatibility is longer than a few years. it can be practically impossible to deprecate stuff, even.

you see a lot of churn in the web ui world because browsers implement new features that new libraries take advantage of. it seems to be stabilizing a bit around react. the developers in the space do tend to reinvent the wheel more.

it's not that big of a deal to me though, because it's a pet project, not a professional product. if i want to show it off to non-technical friends/family, it's a lot easier for me to point them to a webpage than it is to have them install some binary I produce.

having a native gui isn't precluded going this route either, I'd just have a native gui connect via socket rather than interact directly.

> Whereas a WIN32 app (or Unix or other) from 25 years ago probably still runs fine? I can't imagine the same for any web-app that was written for Netscape and now has to run in a modern browser.

Sure, but then I'd have to learn all of the platform specific apis, or go with something like nuklear or nanogui (like i'm doing now). which is fine, sort of. it's not really the development I want to be doing, and it's got a frustrating workflow.

Just due to my background, having started my career in webdev, i feel more comfortable doing ui work in a browser than i do fussing with native or opengl based uis.

Not exaclty -- it looks like it's pretty overkill for my needs

I'm looking for something more like websocketpp[0], or even just grpc without a requisite proxy. uWebsockets looks really promising, being header only, but in the fine print requires a runtime library. unfortunately, none of that ecosystem seems to use cmake, making integrating it that much more of a pain.

why use cpp for this, I'm sure some HNer will ask. the ray tracer itself is using cuda, that's why. I've also debated

- running it as a grpc server and having some proxy in a more web-accessible language

- creating python bindings and using python to make a websocket/http server for it

neither of those are out of the question, but they're not my first choices, because I'd like to keep the build & execution simple. introducing dependencies, especially other executables, is in conflict with that.

i don't need anything particularly scalable -- a threaded implementation, or one using select() would be fine, if not preferable.

[0] https://docs.websocketpp.org/

[1] https://github.com/uNetworking/uWebSockets

I've been using nanogui[0] to fit the bill for personal uses.

To be honest though, I'm at the point where I'd really prefer an easy and lightweight library to setup a http and/or websocket server, and just make a ui in the browser. I've got a simple use case -- I'm just making a simple scene editor & debugging ui for a toy ray tracer.

I know there are a ton of different libraries out there for the task, but that just makes it hard to evaluate the quality of any given library. I haven't given any a shot, I've only gone so far as to look at them and ponder what the size of the user base is, and question if the project will go inactive in a couple years. Or if it's going to require me to pull in some other host of dependencies.

Recommendations from HNers welcome!

[0] https://github.com/mitsuba-renderer/nanogui

With regard to latency sensitivity, with so many cores available, a single core could be dedicated to processing mouse input. Of course, if there's a lock in the way that's held, that's still a problem.

mysql has a datetime type that can be an index, and should be able use for a range scan. that is, with the appropriate data type, it sounds like you would've had a better time...

> [2] Storing the date and time parts separately would have been sensible but the schema was set in stone a couple of years old before I arrived.

The real benefit of postgres*: offline transactional schema changes. mysql would've done a table copy in order to change it. if mysql supported offline schema changes, perhaps you'd have been able to change the data type, solving the root cause of the problem.

* I haven't had the pleasure of using postgres in production, so I can't speak to how effective any given feature is -- only what the marketing appeal is.

There's a world of difference between the myisam & innodb storage engines. Not encouraging you to return or anything, just throwing it out there that many/most storage related problems were because of myisam.

- Turn your sound off - Change how you get notified - Set your editor to fullscreen - give it its own virtual desktop - Learn the keybindings to be able to switch back and forth very quickly

I didn't mean it adversarially, but I can see how you came to that conclusion. Communication is hard.

I was trying to convey that they wouldn't exist because it hadn't been asked for. People aren't mind readers, ops has to vocalize their needs. Which is what the post was doing. And I don't think those needs are unreasonable, either. My point was more that the work to make sure those things are available needs to happen higher up than you'll be able to reach by talking to any individual developer.

> "Own" in this context means be responsible for.

I understand this, this is what I was trying to direct my distaste at. Unfortunately, it seems to have been misconstrued by responders.

> you own and are responsible for the part of that service delivery

No, I'm just responsible for that part of the service delivery. I own none of it.

I object to it in the same way that I object to hearing "we're a family" from leadership.

> If you’re a Software Engineer/Developer, then consider that a service (at least, for me), is a piece of code running in a live production system, that YOU wrote, only YOU know how it works, thus YOU own.

I've grown unfond of this attitude. I most certainly don't own it. I have no IP rights to it at all. We're both being paid to solve different facets of the same problem. Coming at me with "this is your problem" isn't going to foster a collaborative environment with me. Which is much more pleasant than an adversarial environment.

Also: I'm not the only one that knows how it works, it's been peer reviewed in no small part to reduce my bus factor. All documentation requested is perfectly reasonable, and should be part of the organizations standard operating procedure.

If it's not part of the SOP, then no, you wont have those things. You need to work at a cultural level to change that, and for that you're much better off making allies than anything else. Make it clear how those things help you, and what you'll do to make the developers life easier when you don't need to worry about the basics. If altruism fails you, you can usually count on people to act in their own best interests.

> One thing I love about Vyvanse is that it really does have an all-day effect. I'm wired, active, and focused from the moment I take it in the morning, until 11pm or so at night. Unfortunately this also means that it takes a lot of self-discipline to keep a good sleep schedule, which isn't something us ADHDers are very good at, especially as the medication wears off. On just Vyvanse alone, I have a hard time falling asleep and sleeping well.

Interestingly, adderall not having an all day effect is something I like about it. I take an XR in the morning and have a smaller IR in the afternoon. It gives me the flexibility to not take one or the other if I'm not feeling up for it.

> Melatonin is ridiculously safe. It basically has no detrimental effects in large doses. As a result, nutrition companies are in a war to make ever bigger over-the-counter doses because those sell better. But unfortunately while 5mg isn't toxic, it also makes me sleep 10 hrs and wake up groggy. As a result it's hard to find over the counter melatonin that is in the real dosage I want, 0.3 - 0.5 mg.

My sleep doc has advised ~0.5mg a couple hours before going to sleep. As I've come to understand it, taking it too soon before sleep is what causes the grogginess.

> However I found that Costco sells kids melatonin gummies with a 1 mg dosage, which is the smallest you can find on the market without paying extra. I just cut/bite the gummies in half to take approx 0.5mg a night. It's perfect, and I'm sorry it didn't work for you :(

I found some 1mg flavored chewable tablets that're easy to split in half. I've found the same brand at my grocery store and on amazon