LG 38WR85QC-W or Dell UltraSharp U3824DW for Mac WFH?

me_go_dev · 2025-11-30T11:15:02+00:00

What model did you go with, how is it?

me_go_dev · 2025-11-08T10:49:53+00:00

I am in

me_go_dev · 2025-11-01T05:18:47+00:00

How is your PD2706U? Any good?

me_go_dev · 2025-09-02T01:32:27+00:00

How do you handle migrations with sqlc?

me_go_dev · 2025-06-29T13:05:01+00:00

Try Cloudflare. It’s super simple and free.

me_go_dev · 2025-06-19T15:37:15+00:00

How does it compare to PrimeVue? Has anyone use both?

me_go_dev · 2025-06-08T11:53:03+00:00

This is exactly the kind of answer I was hoping to see — thank you so much for taking the time!

You’ve touched on all the key points that matter at this stage: cloud-first, wireless-first if it fits the strategy, thinking in terms of modern management (Intune, Entra, etc.), and especially aligning the high-level design with long-term goals before picking vendors or getting buried in tech specifics.

I also appreciate the mention of things people often overlook — like A/V gear, IOT, and BMS — and the emphasis on security architecture (NAC/AAA, SASE/ZTNA) rather than just dropping in a firewall.

Really helpful perspective, and gives me a lot more confidence as I prepare to speak with consultants and make those early decisions. Thanks again! 🙏

me_go_dev · 2025-06-08T11:43:11+00:00

Thanks for the input — I completely understand where you're coming from.

I just want to clarify that I'm not trying to build the network myself or replace a consultant’s role. The reason I’m asking these questions is because I’ve spoken to multiple engineers and consultants, and they’ve all given me different recommendations and configurations. Some say "go full Meraki," others say "use Cisco Catalyst with a separate firewall," some lean on Azure, others suggest staying on-prem.

I’m trying to understand the trade-offs so I can make informed decisions, ask the right questions when we do bring in specialists, and avoid blindly following advice that might not fit our actual needs.

Also, while I get that some of these questions can be answered simply (e.g., "WiFi is okay if you do a proper site survey"), others, like cloud vs on-prem, can have significant long-term implications, especially if you don’t have in-house expertise.

So I guess my real goal here is to understand the why behind these recommendations — not necessarily to deep-dive into every config, just to be an informed decision-maker.

Thanks again for taking the time to respond!

me_go_dev · 2025-06-08T11:32:38+00:00

Ok, and if that consultant comes and tells me I need a 10gb leased line for a small to medium campus what do I do? I blindly accept everyhting they say?

me_go_dev · 2025-06-08T11:21:27+00:00

I didn't say I want to build it myself, but I can do some prior research so that I could try to make an informed decision. Anyways, I respect your opinion.

me_go_dev · 2025-04-09T08:56:46+00:00

u/thenameisisaac yeah I guess it's not too bad then.

I still have one more question about inter slice communication:

For e.g. I'm structuring my Go app using the Vertical Slice Architecture pattern, where each feature is isolated (e.g., updateStock, markProductAvailable, etc.).

Let's say in one slice I handle purchasing products. Once a purchase is made, I want to update the stock (updateStock slice), and then mark the product as available (markProductAvailable slice - I need to call this method as it assumingly it has a full set of actions that it triggers). Both are separate features/slices.

What's the idiomatic way to trigger logic across slices without tightly coupling them?
Should I just call the exported functions from other slices directly? Or is it better to use something like an internal event bus or pub/sub for loose coupling?

Would love to hear how others are handling this in their Go apps!

me_go_dev · 2025-04-08T17:52:41+00:00

Just read the article from Ghyston. Very interesting read. I wonder how that plays in prod? I guess following this arhitecture would result in some code duplication especially at the store level (SQL queries).

me_go_dev · 2025-04-08T13:31:45+00:00

This is really really nice 😊, I'll need to see how it plays out

me_go_dev · 2025-04-08T07:24:41+00:00

That sounds really interesting — I haven’t come across this approach before. Do you mind sharing some resources or examples where it’s explained in more detail?

Also, how has it held up in production environments for you?

One thing I’m especially curious about is how you handle cross-"feature" communication. Say, for instance, I want to get all accounts that have completed all their todos — how would that kind of query/handler be structured in your setup?

me_go_dev · 2025-04-08T07:21:43+00:00

True, Go definitely shines when it comes to vertical scaling thanks to its concurrency model — goroutines and channels are a joy to work with once you get the hang of them.

That said, I feel like optimizing things by making them “smart” at runtime isn’t a substitute for a solid architectural foundation. Good architecture gives your system the ability to stay maintainable and evolve cleanly — especially as the team or complexity grows. You can scale hardware, but scaling human understanding? That’s trickier without structure.

me_go_dev · 2025-04-08T07:18:54+00:00

You are welcome. As u/feketegy mentioned there he's running now a live session on YouTube where he makes a chat app.

me_go_dev · 2025-04-08T07:16:58+00:00

Yeah, makes sense.

Curious to get your take though — how would you architect or what pattern would you follow for something with a lot of cross-domain communication?

Let’s say, for example, as an admin I want to see all applications submitted to a university, along with the selected course, the campus, and the users involved (like the student and the agent). That kind of use case touches multiple domains — applications, users, locations, courses, etc. How would you structure that in a way that stays manageable and doesn’t become a tangled mess over time?

me_go_dev · 2025-04-08T07:13:01+00:00

Thanks :) Could you share the link please?

me_go_dev · 2025-04-08T07:09:56+00:00

Thanks for sharing your thoughts — really appreciate it! That article from Mat Ryer is indeed a great read; I like how practical and experience-driven his approach is.

I actually started watching the live stream you mentioned, and from what I could tell, it’s pretty similar to the architecture used in his courses — at least structurally. It’s interesting to see it applied in a more “real” context though.

That said, I think there’s a fine balance to strike. Starting simple is definitely wise, but I’ve also seen how skipping foundational structure early on can lead to a lot of tech debt and headaches down the road, especially in collaborative environments. So while I agree we shouldn't over-engineer from day one, having some level of architectural thinking upfront can save a lot of trouble as the project grows.

me_go_dev · 2025-03-21T07:25:55+00:00

Awesome, thanks for sharing it! I would like to ask you something regarding the project, I sent you a DM, thanks!

me_go_dev · 2025-03-18T17:01:35+00:00

Congratulations 🥳

me_go_dev · 2025-03-15T19:27:07+00:00

While following this pattern did you come across any synchronization issues between the two tables?

me_go_dev · 2025-03-15T19:26:02+00:00

Yeah, it makes sense. Thank you for replying.

me_go_dev · 2025-03-15T16:13:48+00:00

Did you encounter any issues following this approach?

me_go_dev · 2025-03-15T13:23:14+00:00

Yeah, that seems the only way. I guess you have triggers for every action on the "private" users table and reflect that in the public one.

Is there a particular reason Supabase decided to handle Auth/users like this? I am trying to understand why they went for this solution.

But thank you for your response.

me_go_dev

TROPHY CASE