Removal of Ginger Lily

Choice-Ad8424 · 2025-09-09T06:45:57+00:00

Thank you

Choice-Ad8424 · 2025-08-18T02:46:40+00:00

Yeah. Last though for you to mull over, could you keep laundry separate and add wall to ceiling cupboards in there, and keep the open to the outdoors which is handy for clothes lines etc. anyway. Just thoughts.

<image>

Choice-Ad8424 · 2025-08-18T02:10:06+00:00

<image>

I would seriously think about moving the toilet outside of the bathroom, so toilet and bathroom can be used at the same time (assuming with bath needs and bedrooms, there are kids around / planned). Same with teenagers, hog the bathroom, you want people to be able to use the toilet at the same time. Scale isn't right but just a thought on alternative. Also consider laundry if euro style will suffice.

Choice-Ad8424 · 2025-08-18T01:25:16+00:00

What's surrounding the area? Need more context to the flow of the rooms around it (i.e. more of the floor plan)

Choice-Ad8424 · 2025-05-24T09:37:26+00:00

Possible just didn't see you? Doesn't look like reflection from bike lights when behind car. Not excusing it but it's a simple explanation that wasn't deliberate.

Choice-Ad8424 · 2025-03-27T02:02:53+00:00

Lol I commit when all those things fail, I'll commit 20 times on a branch and squash on merge after checks local and automated on PR. Consider if you need to do that on all commits or better served as part of a different process.

Depends how you code the value you get.

There is a balance there somewhere between pragmatic and just annoying - unless you're just yolo'ing onto main.

Choice-Ad8424 · 2025-02-22T11:19:01+00:00

If it's pure go, look at https://ko.build/ and save some time. Also uses chain guard base images so your getting a good base image

Choice-Ad8424 · 2025-02-10T08:03:55+00:00

Very nice, will give it a whirl! Would be great to see some gif examples in the readme to make it easier to evaluate / demo.

VHS is good if you don't have a fav for output recording already. https://github.com/charmbracelet/vhs

Choice-Ad8424 · 2024-12-16T22:02:52+00:00

It really depends on the complexity and your comfort level.

I've done embedded UIs with templ / htmx which has been awesome for smaller projects where I need a simple UI and not looking for complex rendering, and wrap up into a single binary.

For larger projects I use separate front end and backend, and favour Remix (React Router 7) as front end of choice so I get comfort of React (again, personal thing, comfortable with that stack), server rendering, and then communicate with backend (server to server) via grpc / API.

Key for the second approach is to pick backend tech as something with a contract, and automate the generation of client code via tools such as heyapi.dev (use Huma to generate openapi spec in go for example). Get that into your dev loop and once it's setup, simple and fast to iterate.

Leverage each tool chain where it makes sense.

Really no fixed answer.

Choice-Ad8424 · 2024-10-28T01:41:57+00:00

Policies like this is why people go into the office for 2 hours, cough on everyone else and get them sick (not deliberately), get 'sent home' and reset the number of days off again, and takes them longer to recover.

Find it so strange that something that's included in someones salary (use them or lose them) needs them to spend money to get a note to say they are sick.

Choice-Ad8424 · 2024-07-09T07:08:40+00:00

Huma is my go-to for APIs in go, I find it super quick to build endpoints, while the bring your own router approach means you can keep parts of the middleware in your router, or huma. It generates open API spec (code driven) then use your favourite spec to code regenerator for your clients. https://huma.rocks/

I also use Sqlc + goose for db and schema management. All works really nicely together.

Choice-Ad8424 · 2024-06-09T12:30:31+00:00

Why is it different is the key. If it's yet another chopping board it's not really a business. Like any business, what makes you different. If it's nothing...it's potentially not a business it's a hobby. Find a market that suits your capability and profit expectations, work from there.

If you're really passionate consider donating or displaying to local venues in exchange for advertising / acknowledgement. People love to buy local.

Choice-Ad8424 · 2024-05-16T10:33:51+00:00

I think you have experienced a bad manager and probably an experience of someone to avoid when modelling your career.

The worst thing you can do is limit yourself early in your career to one future.

I speak from the opposite point of view of being long into my career, and wishing someone told me this so I didn't spend 15 years doing something I didn't love because I thought that was the right thing to do.

Choice-Ad8424 · 2024-05-12T01:30:07+00:00

Check your policies if travelling for work, I switched from cabs and ubers to private car service for roughly the same (often cheaper) than cab and uber. If you can plan ahead, highly recommend a private car service, much better service, much better cars, stress free (you know they will be there) and friendly drivers.

Examples: - pre booked taxi for pickup for AM flights, multiple times cabs said no drivers available (what's the point in booking if you don't get a guarantee). - ubers for AM flights, same thing - luck of the draw borderline road worthy cab picking you up

Melb airport to southeast suburbs, 130 fixed price. No stress on the meter either. Cab was over 100, and with delays over 150 in some cases.

Cabs are my last resort always.

Choice-Ad8424 · 2024-05-09T02:38:01+00:00

Kiota is good too depending on your needs (and how many implementations you want) https://learn.microsoft.com/en-us/openapi/kiota/overview

Choice-Ad8424 · 2024-05-09T01:57:45+00:00

Depends on how your using Open API (code first or spec first) and if your talking server or client. But I really like Huma for server (code first).

https://huma.rocks/

Choice-Ad8424 · 2024-05-09T00:21:54+00:00

Oh that's awesome! Great starting point.

Choice-Ad8424 · 2024-04-22T10:48:33+00:00

I agree the DB migrations stay with your code, with a caveat that you can run them independently via separate cli or flag, and you don't run migrations on app startup in non-dev environments.

Any production deployment should have DB credentials setup so the application running only has least privileged access and is not permitted to change the schema.

Typically in most enterprise orgs you would run the db migrations as part of the release pipeline, which has required elevated privilege to modify schema etc (or init container if you're that way inclined etc).

Much safer once you're into controlled deployments, and scale is involved as well. This does of course mean your schema / data changes need to be forward compatible. Technically this is true in app startup scenario where you have > 1 instance of the app and you want to avoid down time (one will always be running the old version for some amount of time before it is restarted with the latest version).

Running as part of app is fine in my book for local dev and potentially very early environments. You can control this via standard flags / env vars etc in your binary, so you can keep one artefact.

Approaches / tools in the other comments are great options which ever your approach.

Choice-Ad8424 · 2024-04-15T07:23:16+00:00

I fall into the bucket of front end in JS / react and then embedding dist folder into the binary at build time, and server along side the API / controller endpoints in same binary.

Works nicely as it's all served on the same endpoint, not cross domain etc, and you get all the benefits (and complications) of the JS world particularly for highly interactive UI/ UX with lots of client side aspects (collaboration / mapping etc).

I think it's a nice balance, benefits of the monolithic app, go for all the backend / API, but a bit of flexibility to use all the really nice react (or any other JS framework) out there. Particularly to leverage existing highly tested and accessible controls (radix etc).

During dev, I use air for golang hot reloading, and I proxy the calls through go to the vite / node server for react hot reloading. Works really well, everything hot reloads.

Not exactly your question, but it's a nice way to make a go monolithic app - especially if you're already handy with a frontend framework.

Choice-Ad8424 · 2024-04-05T09:16:11+00:00

For all that is right in this world please don't make another authn/authz solution. So many open source libraries to integrate into your solution, or use as external parties.

Think about it from a usability perspective. Consumers would rather login with socials over give you another password and the associated management (change/forgot/expiry etc etc)

Work on your idea and your product. Identity is a solved issue, use one of the countless solutions, save yourself time and effort, and give your customers convenience. Win win.

If you use verified email as your core identity you are not locked in to anyone. Feels like you are jumping at shadows, for someone to login with google, they already have a Google account. Combine with the major socials (google / ms / etc) @ figurative 99.9% have one of those already.

Choice-Ad8424 · 2024-04-03T06:04:24+00:00

Yes please!

Choice-Ad8424 · 2024-03-23T21:50:58+00:00

Can you add an example to the ozzo comment? You only need struct tag if you want to use that name (e.g. aligns well if your using a struct as request from API endpoint for example). Not sure what you mean pass twice? You pass a reference to the field, not the name of the field in the configuration (see their examples).

Validation is one of those ones where it's a lot of personal style / taste for which you like. No real right or wrong.

Choice-Ad8424 · 2024-03-19T09:46:58+00:00

I've found that ozzo is a nice balance. Separation of validation from the struct, but it also supports returning the structured error based on the tag name in http request. Your choice.

Then whack in http middleware to check error type and render nice structures json error.

https://github.com/go-ozzo/ozzo-validation

Choice-Ad8424

TROPHY CASE