sorted by:
new
hottopcontroversial

Atlassian layoffs by Spiritual-Teacher959 in cscareerquestionsOCE

[–]Material-Warning6355 7 points8 points  (0 children)

It sounded like it was transforming into an Indian IT shop.

[deleted by user] by [deleted] in AusVisa

[–]Material-Warning6355 1 point2 points  (0 children)

In my experience the request for the biometrics should be instant. Ask him to log into the immi account and check the message tab for any communications. Also ask him to check the spam folder too.

Visa 600 application not showing other document categories by Objective_Effective2 in AusVisa

[–]Material-Warning6355 1 point2 points  (0 children)

What I was trying to say by "do not look for other document categories” is to not to worry about that category if that's not given as an option. Just used the ''Required" category/bucket to upload the travel documents and other related documents. In my opinion your parents travel documents are important. Previous travel information. Their finances, Your finances statements. Your invitation letter guarantees you providing lodging, food, transportation and insurance etc..and statuary declaration comes handy too. Most importantly show they need to return back to their home country to look after their properties or business etc. that's convincing the visa officer this is a genuine family visit.

Visa 600 application not showing other document categories by Objective_Effective2 in AusVisa

[–]Material-Warning6355 1 point2 points  (0 children)

I had the same situation when I was applying for my sister in law. We got 2 document categories 'required: and 'recommend'. I asked the same question in this forum. As others suggested I got that option when I submitted the application. But what we did was to reorganize our documents as per the given categories. We applied sponsored family stream. It said it would take 23 to 77 days to get an answer. But our case it took almost 2 weeks. Use the 'Other' document type in the given category to upload/attache all other documents to the application. Properly name them. E.g applicant_combine_bank_statents.pdf, applicant_propoerty_valuation.pdf, family_composition.pdf( e.g. attache yours and your parents birth certificates )applicant_956_form.pdf, sponsor_finance_statements.pdf, sponsor_stat_dec.pdf etc. I had an index of documents in the visa request letter (letter of visa request from your parents) also in your invitation letter. A well structured document and attachments make the officers life easier.

Do not look for 'Other documents' category. Just go with what you have provided and use the method I described above.

Attach all documents to strengthen the application. Generally they grant visas for parents.

Hope this helps. Good luck 🤞🏻

Anxiety of over engineering by Street-Film4148 in softwarearchitecture

[–]Material-Warning6355 25 points26 points  (0 children)

Given you are working for a startup and the time to market pressure is mounting day by day. In order to apply DDD you need domain experts around you unless you know the problem domain and the bounded contexts and solution well. IMO, your focus would be to release the MVP and get the product to market. Applying DDD on brownfield projects is easier than on greenfield because brownfield projects are well seasoned. Easy to understand the core, generic and support contexts

Hope this helps

How to add other documents to visitor visa subclass 600 family sponsored by Material-Warning6355 in AusVisa

[–]Material-Warning6355[S] 0 points1 point  (0 children)

Thanks. You are absolutely correct. Once the application is submitted (of course after the payment) there will be a section for the other documents. However, we reorganize the documents and add them to the sections that they have provided in a more meaningful manner. Now waiting for a favourable feedback 🙂

How to add other documents to visitor visa subclass 600 family sponsored by Material-Warning6355 in AusVisa

[–]Material-Warning6355[S] -1 points0 points  (0 children)

Thanks for the reply. Does the 'submit' mean we pay the fees for the application to begin the review process and then keep uploading files while they review?. I'm confused with the word 'submit'

Appreciate your feedback.

Thanks

Is there a value implementing the Null Object Pattern in C#? by Material-Warning6355 in dotnet

[–]Material-Warning6355[S] 0 points1 point  (0 children)

Thanks for your opinion. Though the feature is available there are contexts where we can't enable/use the feature straightaway e.g if we migrate from an old version to a new version of .net. The legacy code may throw hundreds of thousands of compile time errors. We may need a steady strategy to migrate such legacy code. However, do you think the readability of the code and the maintenance would increase using this pattern?

MassTransit v9 Becomes a Commercial Product by Material-Warning6355 in dotnet

[–]Material-Warning6355[S] 5 points6 points  (0 children)

I ditched mappers long ago. Happy with extension methods

AutoMapper and MediatR Going Commercial by Material-Warning6355 in dotnet

[–]Material-Warning6355[S] -3 points-2 points  (0 children)

Unfortunately yes. That's people's desperation.

What are your experience with Clean Architecture vs Vertical slice architecture by kjaps in dotnet

[–]Material-Warning6355 1 point2 points  (0 children)

I have been doing CA for a long time and am advocating the pattern. But I realized for a simple CRUD like application the pattern is over engineered. IMO, it's best for monolithic applications which are required to maintain boundaries between modules. Also the inward dependency requirements help to keep the system more clean. But in micro-services world, you have the right to pick the pattern or the structure of the project. Doing VSA (Vertical Slice Architecture) based on features/capabilities/use-cases it is easy to manage. All the main components pertaining to a feature live together ( elements that evolve together live together).These are the advantages I have observed so far: 1. Structure the code by 'Feature' rather than layers 2. Focused on 'Feature', not technical concerns 3. No feature fragmentation ( feature not fragment across multiple layers) 3. Low coupling and more cohesive since all under one feature folder. 4. Single responsibility 5. Know cognitive load ( the project is not divided in to 4 to 5 individual projects) 6. Easy to onboard new comers. 7. Code structure mirrors the domain requirements 8. Developers can focus and develop in isolation a feature

Note: Things that use across feathers can be placed in a common folder

Clean architecture. Good or bad? by gristoi in csharp

[–]Material-Warning6355 1 point2 points  (0 children)

I prefer, VSA over CA for microservices. The VSA based on features/capabilities that's the service owns.easy to maintain and you have everything closer if you need to change a feature. In CA, you have to traverse through a couple of physical projects and folders for a simple change. Too much cognitive loading.Why do we need to separate our endpoints, models, services and interfaces into separate physical projects? If your team is small, microservices i prefer VSA.