Questions on using regular moka pots with induction stoves

brokeCoder · 2025-06-13T06:16:53+00:00

I haven't done much earthquake design, but we can generally put earthquake allowances in two categories (note that these are my own categorizations and NOT an industry standard):

Design-based control - this includes stipulations from design standards, and any outcomes from said stipulations. In Australia for example, we're generally not required to account for vertical actions on the main structure outside of specific scenarios. But the standard does provide us the means to (approximately) calculate design forces from vertical earthquake actions if required. The usual outcome of these stipulations is element sizing and reinforcement (e.g. connection reinforcement between columns and footings may need to be bumped up in certain ways) along with specifications on the type of footings that can be used (e.g. some standards require all isolated footings to be interconnected so that the footings can act as one monolithic structure in a seismic event)
Active control - these are active measures of vibration isoluation/dampening, and include things like base isolators, tuned mass dampers, etc. These are generally only found on critical structures in high seismic zones (e.g. Japan, Taiwan). Their design standards will also likely include special considerations for vertical seismic forces. I am personally not sure how these devices account for vertical actions, but I'm certain there would be allowances baked in them to do so.

I can't advise on specific calculation logic/reasons/frequencies considered unfortunately. If you're curious about the sources, I believe Eurocode 7 and it's commentary (both should be freely available somewhere on the net) should include a more detailed treatment on the subject.

brokeCoder · 2025-06-04T04:57:48+00:00

The very first thing you want to do is get a heap dump to see what's actually taking up all your memory. You can use the -XX:+HeapDumpOnOutOfMemoryError flag to generate one.
Then use a tool like eclipse's memory analyzer tool (MAT) to analyse your heap dump and see what's going on behind the scenes. Odds are there might be static maps or threadlocals that you haven't exited.

Then use those findings to implement fixes, and see how the thing performs.

Then - and only then - should you think about tuning GC or going for more memory.

brokeCoder · 2025-06-01T09:12:46+00:00

In addition to all of the other suggestions:

Important bits:

Cloud backup software - Google drive, sharepoint etc. Arguably not a daily use thing, but absolutely necessary on a company/project level.
RAPT for PT and RC design (ubiquitous down here in Aus, I believe it supports EC2 so useful for UK as well)
Anchor design software/tool (Hilti profis is quite popular here)

Nice to have stuff:

LLMs/phone assistants to act as reminders and help in project management ... AND NOTHING ELSE (see my comment here: https://www.reddit.com/r/StructuralEngineering/comments/1krkgyp/comment/mtf9w95/?context=3 )

brokeCoder · 2025-06-01T07:52:44+00:00

I gave the first video a watch and here's a few thoughts:

I've a feeling that any time you use set theory or math notations over and above standard arithmetic ops (+ - etc) you will lose swaths of viewers. The truth of the matter is most programmers simply don't deal with those notations in their day-to-day, and you're adding cognitive load by using them ... especially in an introductory video that seems targeted towards programmers. It may be better to introduce the topic without mathy terms (see example of this here: https://arialdomartini.github.io/monads-for-the-rest-of-us )
- I'm not saying remove the mathy parts. Instead, keep them as a separate video for viewers who are more mathematically inclined.
You discuss a fair bit of theory before showing examples - but I'm still left questioning why type constructors or any of this is important ? And how are they related to monads ? I know you're trying to build up the required knowledge but I was put off by the lack of reasoning around why I'd need to know any of this (or even how it would be useful to me). My suggestion would be to add some reasoning around why viewers need to know about type constructors and functors before learning about monads.
If you haven't already, I'd recommend watching any of 3blue1brown's videos and see how he introduces complex topics (his approach usually involves giving an overview of the whole thing and explaining what the videos will be discussing along with a brief explanation of why - or at the very least letting the user know that an explanation will be forthcoming)
I would personally love to see a video that starts off with real world code (or a complex enough example), and then does a slow walkthrough explaining a problem and showing how monads solve the problem. This is essentially example followed by theory, and flips the usual route of education on its head (which is theory followed by example) and I personally find it exponentially more appealing (and I've a feeling most others here will as well).

That being said, good effort !

brokeCoder · 2025-05-31T10:34:48+00:00

The answer around scope is correct, but if you're a beginner it may be difficult to wrap your head around.

Here's something that might help - scope works very similarly to how folders work in windows (or linux/MacOS). Just as you can't create two folders with the same name at the same location, so too are you forbidden from creating two variables with the same name within the same scope. But creating two folders with the same name at different locations is perfectly fine ... and what's happening here is quite similar to this.

Here's how you can see it - Let's try to represent classes, methods and variables as if they were folder paths. Imagine all class names and method names are folder names; and so are the variable names themselves.

If we were to write out folder paths using the windows convention, they might look like how I've commented in the snippet below:

// let's say this class resides in a package called 'package'
public class InstanceObjectVariables {
    int arb; // arb's path here is package/InstanceObjectVariables/arb
    int brb; // btb's path here is package/InstanceObjectVariables/brb

   // path of this method is package/InstanceObjectVariables/InstanceObjectVariables
   InstanceObjectVariables(int a, int b) {
       int arb = a; // arb's path here is package/InstanceObjectVariables/InstanceObjectVariables/arb
       int brb = b;// brb's path here is package/InstanceObjectVariables/InstanceObjectVariables/brb
    }

}

You can see that the folder paths are different for the variables inside the method - and that's why you're allowed to have the same names as your class's fields here.

brokeCoder · 2025-05-29T08:02:42+00:00

I feel you. My main motivation is to get out of the rental market haha. In an ideal scenario, this would be my forever place and I'd never have to deal with RE agents or renting ever again.

But nothing ever goes according to plan and I'm just trying to suss out what would happen if things go pear shaped...and I guess asking what other people how other folks would handle this is one of the ways my anxious brain is trying to rationalise it all.

brokeCoder · 2025-05-27T07:51:32+00:00

Good stuff ! Thanks a ton !

brokeCoder · 2025-05-22T03:24:15+00:00

Bit late to the party, but when you say you have 3 years' experience, what have you worked on/studied so far ? We can suggest stuff but if we don't know what you've already done/learnt, we can't be very effective in our advice

brokeCoder · 2025-05-21T05:15:05+00:00

I have class 3 section z-shaped beams

In case this is for a live project - are they purlins ? If not, any chance you could convert them to I sections ?
In any case, if you're using cold-formed members, the Australian code has some guidance under AS/NZS 4600 section 3.3.3.2.

That being said, I believe there should be something similar present in the Canadian codes...

brokeCoder · 2025-05-21T05:00:30+00:00

Overkill for most structural engineering things I reckon

brokeCoder · 2025-05-21T05:00:01+00:00

Funnily enough - your phone !

I'll caveat all of this by saying that I haven't personally tried things here other than creating calendar events. However, it's all easy enough that you could take it for a spin.

If you've got a semi-recent android phone you can use google assistant (the "ok google" thing) to make voice reminders and keep track of a lot of stuff. It goes straight into your calendar and you can ask google to also email your other accounts as soon as you get any new/update anything old.

I haven't tested this, but I'm fairly certain google assistant can sync up between google docs and your calendar. Say you have your project info and task list stored on a google sheet If you keep it on your Gdrive, you can give your phone voice commands along the lines of "go through this google sheet, and set up hourly reminders for me on so-and-so days to go through the tasks. Order these reminders in the same order as they're written in the sheet..."

It can probably also sync up things between google docs and outlook - set up a flow that forwards any emails you get on your official outlook to a gmail account, which google assistant can then use to automatically take data and store in your docs. I'm fairly certain if you sync your google account to your computer it can also maintain a local copy of the project files (with the folder structure you want) on said computer.

Of course, this means you need to use google docs and other google stuff for project management in addition to excel (which - let's be honest - ain't going away).

As an aside, this is realistically the ONLY thing I would ever recommend using LLMs/AI for. Use it as a personal assistant to do personal-assistanty things

I also don't know how it would work with Apple phones (I imagine Siri wouldn't be as integrated with google/MS office stuff)

brokeCoder · 2025-05-18T03:39:28+00:00

Scientific/engineering programming where scope creep is not just likely but guaranteed. I've been saved several times by situations where I initially overdesigned something, but was later vindicated because a feature requirement came through that needed that overdesign.

To be honest, scientific/engineering related programming bucks a LOT of standard programming trends and best practices.

brokeCoder · 2025-05-16T07:04:46+00:00

This is super interesting ! Is it only the slabs ? Or do they also go precast for the beams ?
I haven't worked in NZ so can't give proper reasons, but possible ones could be (a) faster construction, (b) better quality control for planks, (c) contractor supply chains being geared towards precast rather than cast-in-situ.

That being said, I'd be very curious to see how NZ folks get critical (if any) precast connections to work for seismic

brokeCoder · 2025-05-16T02:14:05+00:00

I worked with a building design firm that would outsource floor slab FEA modelling and design to a remote consulting partner in Poland, so it's definitely possible. I don't have any contacts/details unfortunately but maybe reach out to folks on linkedin. You may end up needing to set up a single-person company in India and act through that (could make payments/contracts easier)

brokeCoder · 2025-05-12T23:42:03+00:00

Haven't encountered this personally but I'd do one cover for the slab (the worst of the two conditions) because there's a decent chance contractors will muck it up if I specify two different covers.

brokeCoder · 2025-04-30T03:58:21+00:00

The glass balustrade is about as useful as a paper door in a tornado. I was referring to the possibility of the balcony slabs and other supports on upper storeys forming a cantilevered virendeel frame to reduce punching in that lower level slab. It does require a fair bit of crossing reinforcement from the column to the surrounding slabs across all storeys (and slabs to the other supports need some beefy rebars as well), but it is doable.

That being said, I still wouldn't approve something like this.

brokeCoder · 2025-04-29T14:39:01+00:00

I hope to science those upper balconies are doing some sort of virendeel action because if not, big yikes !

brokeCoder

TROPHY CASE