marklubi

https://github.com/jelly-org/ui

It's buried at the bottom. Had to click on the "sponsoring" link, and then select the package.

Feels like they should make the repository more prominent.

Thanks for sharing the video of moving the server.

I wouldn't say that I miss those days, but there's some good nostalgia there having done some things that feel pretty similar (early 2000s). Not quite to that extreme though.

For the project I've been working on for more than 15 years, we make extensive use of the pub/sub functionality for distributing live data. Pub/sub scales well across the cluster. Publish to one, and it goes out to subscribers on any of the nodes that they've connected to.

Will millions of users, high availability is critical for this functionality.

It reminds me of a rant that my friend sometimes goes on with regards to really low quality items, particularly about music...

someone wrote it, someone performed it, someone mixed it, someone approved it, someone developed marketing for it, someone helped get it on shelves, and then someone played it.

There were plenty of points along the way where the disaster could have been averted.

The popping sounds from a turbo car is from the wastegate (whistling sound for a blow off value) when the system is releasing pressure from the turbo that was built up. It prevents over compression that would damage the engine.

I was thinking a similar thing. Many of our customers have purpose use computers that rarely see physical infrastructure internet, but need a modern browser (many chose Chrome on their own, we never recommended it).

They're going to get blasted with cellular data charges when they fire up their computer in the field.

Documenting why is incredibly important, but also why something has not been done.

The last business I started, I was coding at full steam building features that I could make work now although not optimal, so I would add comments reflecting that.

Over the > 15 years the product’s been on the market, there have been several times I’ve come back across those comments when we outgrew the quick solution several years later.

They enjoyed each other's company and bonded over these shared experiences

My son competes on the national and international level in two different sports, so we do a lot of traveling. The bonding is very important, just as it is knowing when to get out of the way and let them shine.

In one sport, I drop him off and pick him up for practice (he gets distracted/flustered when someone is there watching him practice). In the other, I practice with him and am trying to stay better than him as long as I can.

There are a few other things I think are important...

If they don't want to do something, don't push them to. My son decided not to compete in a national ranking event in a couple of months because his competitions are on Thursday and Saturday and he would miss three days of school when factoring in travel.

Try to anticipate their eventual needs and make sure the right tools/equipment/etc. are available for them before they realize they needed it. Also, have backup equipment just in case something breaks or fails.

Make sure that they understand the 'why' behind all the things that both they have done, and what you have done, to enable them to get to that level.

Finally, from a young age, teach them to "always do your best, and always do better next time." The first national competition he went to, he literally finished dead last out of over 250. When we were in the airport heading home, I let him know that it's alright if he doesn't want to do more of them. He didn't back down in the slightest, and asked me when the next one was because he knew he could do better. Next month will be the second time he competes in the Junior Olympics for that sport.

Haven't noticed that one. Oxidation perhaps, or maybe salt in the air based on the locations?

West coast food (particularly oysters) seems to be a little bit more salty/briny.

Similar thing with orange juice. The producers add 'flavor packs' to adjust the taste for different regions of the US.

My son and I travel all over the US for various competitions, and there are certain regions where he refuses to get OJ because of the flavor differences.

This is a terrible video. Doesn't even have dates right. ECUs have been locked far before 2017.

I don't like the lack of buttons/knobs for things like heat (they can be configured based on the weather though), but most of his complaints are just trash.

The S58 engine is spectacular, the handling on the 2024 M4 is amazing.

My only real complaint is when the CarPlay integration comes up as "Unknown Song, Unknown Artist" and I have to change the media source to get control of it from the steering wheel buttons.

They already have a monitoring system... TPMS. Four distinct IDs for every vehicle passing a location makes for a good fingerprint (they've been using this for years to estimate traffic levels)

Add in something like Flock license plate reading and you now know which vehicle it was.

Bought my teenage son a couple lock picking kits, he's picked almost every single lock we have in our house.

I then picked up a sizable rock, and told him I could get into the house faster than he could. He didn't understand for a few moments, but the lesson was learned.

He wrote Thrones explicitly to challenge Hollywood clichés

Hard disagreement on that one.

He wrote an epic story known as A Song of Ice and Fire (started in '96) that ended up getting out of hand and tied up with too many Goordian knots to complete. Sadly, we'll probably never get a conclusion to it.

Along the line, a producer came along who thought they could make money with it. First few seasons weren't terrible, but were too short to capture it all. The rest were completely rushed and unable to take on all that was going on. They went off the rails after a few seasons.

I will agree that he doesn't owe anyone anything though. My philosophy is that I create for me, if others also enjoy that, excellent.

Edit: I'm still a little bitter after going to a trivia night and losing a question because I gave the canon answer that was different from the show

This reminds me of the internet in 2000

The thing that changed it was smartphones (~7 years later). Suddenly, the internet was available everywhere and not just a thing for nerds.

Not sure that AI is quite there yet, currently trying to identify what will be the catalyst that makes it seamless.

Similar story for me. With my work, I get pulled in a lot of different directions at seemingly random times. This helps me quickly resume what I was doing.

I can confirm this. Have a relative that works for Apple. Made the mistake of complaining in front of her about their take on sales (they make six-figures annually from my app). She went off on how much they give us (including Xcode) for the privilege of having an app on their phones.

Still don't have a contact there. Would have thought I would at least get someone there to talk with if issues come up.

Every time there is an Xcode update, I dread installing it because it will be a whole bunch of new bugs, and I just finally figured out the previous ones.

I wish. It's on Github, but my hands are tied and I can't share them since it's someone else's property now (hooray for exits, I think).

It's mostly a thought process...

I have or need something (entity), lets get data about it (repository/extensions), we need to do something with this now (only extensions).

Lots of "static" and "this" involved, but the separation and eventual simplicity makes it worth the effort.

Edit: I tried going through some of them to anonymize some for examples, but it felt like treading in dangerous territory.

Thanks for taking the time to respond. Ultimately though, most of those aren't required from the beginning, but the syntactic sugar, abstractions, and performance gains from them are amazing.

You probably already know, but I'll opine a little bit about extension methods. I use them a lot.

Entities > Repositories > Functionality. All split out.

- Entities (pretty much just gets and sets, nothing more than necessary).

- Repositories via extensions to determine where the data comes and goes from (some data comes from SQL, some from Redis, some from Postgres, doesn't matter since it's split out) and any particular queries you need for optimizing things.

- Functionality via more extensions without adding additional code to the entities.

Separation of purpose/use.

I may or may not have completely replaced our data layer in the middle of the height of our season with no interruption. Little bit passionate about this one.

27 years ago!

Sometimes, I feel like I'm the only old guy on here. BASIC, VB6, .NET, and some Java along the way.

Too many new ones to list, although that might be a whole other problem in itself.

.NET is amazing and keeps getting better. JetBrains is killing it with their IDEs and add-ons.

Currently running nearly a dozen different services written in .NET running on Alpine in K8S.

Started transitioning most of my code to .NET Core/Standard when they first came out. Sadly, I still have to deal with some ASP.NET MVC code that was written before and requires .NET Framework

C# is amazing. Decisions at the education level were made well before it went cross-platform though (FWIW, I've been using it since before v1.1).

Would be interesting in what confusing syntax you're referring to. I think one of the beauties of it is that it's additive. You can program plenty of simple stuff in it with conventional style code, but there's a lot of syntactic sugar available that makes things so easy when you need to start scaling things.

Outside of the mystical incantation of `public static void main(String[] args) {`

I don't think it's mystical. If you don't have an instance of the class yet, you need a starting point and static fills that void (lol. I'll show myself out)

I concur with most of your thoughts, except that Java is never going away. I might wish that it would, but here we are.

Not going to disagree. It's the sandbox that we're playing in though (dealing with, HOORAY JAVA!) since it's a class at school.

Have to start somewhere, teach them better alternatives as they evolve. Not even going to broach the prototype-based programing stuff until he comfortably has the basics understood.

Edit: I don't GAF about downvotes, but I would at least expect a response about why. If you don't like the philosophy, give me some reasons. Don't like something else, tell me why. I'll happily debate anyone all day long

I fully disagree with Java as a starting point and it was an interesting conversation with the teacher.

Apparently, "College Prep" courses more or less determine that Java is the language that they should use.

His teacher thought it was stupid as well, but sometimes your hands are tied. That's what the schools are using as a starting metric though.

He was apparently the only person in the class that said he wanted to do software engineering. Don't worry, he'll be a polyglot before he reaches college.

One of the things I've tried to teach people I've mentored over the past few decades is the principle of "Sharing is better than assuming." If you know something, share it with other people.

Definitely agree with this in principle. My son and I play pool (billiards) competitively. As you get better, almost nobody shares any tips because it's very competitive. I've taught him to be better than that and we have a great league team where everyone is helping the others grow.

In the mentoring (not just teaching) realm, I like to guide them into asking the questions that gets them to the answer they're looking for. When the connections in their mind light up, it's amazing.

Beginners have to be nurtured through lots of context that builds up slowly.

My son is 17 and very interested in programming. Had to explain to him public, private, internal, and also static the other night.

I then joked, you should ask your teacher about recursion tomorrow. He's with his mom this weekend, but I'm anxiously awaiting hearing how that went.

what gives the most satisfaction (even though this kind of satisfaction happens very rarely) if I discover some very elegant structure behind whatever has to be implemented that changes the whole way how you thought about programming

A number of years ago, I wrote a caching/lookup library that is probably some of the favorite code I've ever created.

After the initial configuration, the use was elegant and there was really no reason not to use it if you needed to query anything that could be cached on the server side. Super easy to wrap just about any code with it as long as the response is serializable.

CachingCore.Instance.Get(key, cacheDuration, () => { /* expensive lookup code here */ });

Under the hood, it would check the preferred caching solution (e.g., Redis/Memcache/etc), followed by less preferred options if the preferred wasn't available, followed by the expensive lookup if it wasn't found anywhere. Defaulted to in-memory if nothing else was available.

If the data was returned from cache, it would then compare the expiration to the specified duration... If it was getting close to various configurable tolerances, it would start a new lookup in the background and update the cache (some of our lookups could take several minutes*, others just a handful of seconds).

The hardest part was making sure that we didn't cause a thundering herd type problem with looking up stuff multiple times... in-memory cache flags indicating lookups in progress so we could hold up other requests if it failed through and then let them know once it's available. While not the absolute worst case scenario, you might end up making the expensive lookups once from each of the servers that use it if the shared cache isn't available.

* most of these have a separate service running on a schedule to pre-cache the data, but things have a backup with this method.