@Sid2006 @tonnoman

Its not that i dont want to do my own research, its that i dont know where to start it, and it just seem like such a big topic that confuses me alittle. Im working 70hr+ week (fulltime emploed and started my own business) with kids and a wife, so this post was meant to not to get the solution, but get pointers to solutions so im able to study some recommendations and start from there, i know the traffic needed, i just know nothing about cloud hosting- so thanks for the cloudflare mention, ill give that a look.

I do go exploring outside my core areas, im a web dev mainly doing react - so i take design/ux courses and try to get the design experience aswell to be more of a ‘complete frentend package’.. i also take courses further from my main tasks, eg just finished a GoLang course which was pretty exciting..

@jiraTicket so rather than strictly doing risk analysis on all stories, spend the time in the risk analysis productively by askimg where we see risks and onyæ do assesment and mitigation plans on these ?

Sounds like way less time consuming than what im doing at the moment..

Also one of the main issues is when we do see a story we want to riak asses, we often dont know the implementation detail yet, how would you go about this ?

@jiraTicket completely agree!
We currently do have a pretty large testing effort, we have 3 months sprints and the whole 3rd month all devs do exploratory testing and non functional tests(portability, compatability, etc)

Issue is that these defects we do find often could have been fixed way earlier, or come years down the line on some unused feature, and fixing these defects upfront would effectively decreasing price pr bug due to dev in fresh memory, extra rework costs, etc..

@devphobe i completely agree, my biggest issue is i cant get management to put in time to reach the INVEST model of our stories, specifically i cant get a acceptance criteria, as most of our stories actually ets implemented with a very loose acceptance and us deva get to influence how the stories are accepted during development 😅
So ive got issues trying to produce test cases beforehand as stories are not always testable until story is implemented 😳

@spongessuck well complete proactive testing might be impossible, but reactive testing - eg exploratory testing that we do at the end of our sprints to uncover defects must have a counternpart to be defined reactive therefor i just used the term proactive to describe things like unit and e2e 👍🏼

@RememberMe i am releasing it at some point and for now I have just made a placeholder name, but that placeholder name goes into every component name/documentation/e.t.c so I feel like a placeholder name starts to be a bigger and bigger refactor the more I produce 😅

@p100sch god damn, if i could upvote 100x id smash that button!!!

Thank you ever so much, did exactly the trick!

Could you by chance break it down in babysteps/query 101 what you did there? I havent really worked with not exists before so this puzzles my mind alittle, and id like to know what happens under the hood here 🤔😅

@p100sch exactly and that is what i need my select to figure out, it should tell me what level an item needs filled before it has all levels so in the example you just mentioned the sql select should give me

Something like

Level 2 - item 3
Level 2 - item 4
Level 3 - item 1
Level 3 - item 2
Level 3 - item 4

This i can then use to know what gaps i need filled so all levels has all product types in the factor table 🤔

@highlight @p100sch first of all, my description might have been bad, and thanks alot for helping out! But this answer just gives me all product names all the time for some reason 😅🤔

Also Didnt know <> but just googles it, thats a nice operator

Also verry sorry, i need to get the levelnames that isnt precent not the product names

I need it so when i ex make a new product, and add a record in factor with that fk to the new product and an fk to an level, i need to know the levels which still needs to be set together with that new product in order to have a combination of that new product x all levels in the factor table 😅

@possum might not need to be compiled, havent tried publishing this type of project before :)

All i know is that webstorm dont seem to have a publish option, and also i get no bin/out folder when running the project.

Its just html/css with JS/jquery/ajax

@vomitmachine tried importing to VS but i couldnt figure out how, and as for local system deploy, webstorm dont seem to make either a bin/out folder when compiling, so cant even copy files from there and put into IIS :(

@vomitmachine nope 😅 all i've hot is an IIS server, API i made in visual studio (thats published fine) and webapp made in webstorm that i just cant find any documentation on how to publish 😅

@possum im thinking normally, a projevt would have a setting to publish, if not so, you could usualy compile it and then take the files from the bin/out folder, but i can't seem to find either of these options at webstorm, and it doesnt even seem to make bin/out folders when i run the project 🤔
Should i be using another IDE, is webstorm even capable of publishing like e.g visual studio ?

@IntrusionCM @SortOfTested @Voxera so i found my issue was with state handling of the entity's.. the add method of EF will always set an added state to the entity and its related entitys(the navigation properties) and added state will always make an insert. So i iterated through the hashtags to find those already loaded in context, detached those and usef update insteaf og add. (Autogenerated primary keys will if null insert, if not null update) and thus problem got fixed. I can now insert the idea with hashtags, both new and already existing ones from the db 👍
Thanks for the pointers to the right direction all 👊

@GiddyNaya haha 😂
Well the issue is that i .add(idea) (meaning in sql INSERT idea) and expect EF to know wether or no its related entity's in the DB already... Dont EF do that for you 🤔🤔

@Voxera exactly what i am trying to do, but EF makes a insert command instead of update to the DB 😅

@nitnip uh any good resource for me to look on this token thing, or could you explain ? I know it was just "no log in auth" so if it can be done without i guess it is fine 👍👌

@nitnip surely, thing is.. client dotn want any auth. What so ever -.-

@gronostaj alright, i think ive gotten to the conclusion about when you use the properties of C# thanks for the chat my guy, always nice to reflect with someone about solutions and best practices.

After this discussing i might be inclined to use properties, and when necessary throw exceptions -> ill have a talk with my teachers about this again mext week and challange them with this discussion :)

Thanks for the help and chat !

@gronostaj
While i do see how it shortens down code, it still do not address the issues im concerned about, validation on setting 🤔

autoproperties cant have validation, else it should be manual property and then the code isnt that much shorter than a getter/setter method,i just want to be consistent about what and when i use either.

and as the only argument is prettyer code, and not perfomance gains/less maintainence (as maintainence of either type of setter/getter is the same within the {} after they are implemented)
I dont see the benefits outside of bindings.. else i see benefits in implementing the get/set methods due to validations, non silent failures and futureproofed usage...

The only reason i could see properties do the same, would be if we take the validation into a method called validateFoo()
{
//Validation code here
}
And then used the set of property after validated input.

Or if we used property with throwing exceptions, which generally people dont want ? 😅

@gronostaj i think im starting to get what you'r meaning :)

So. Let's say in class Person{}
Rather have a method checkAge() that the property can use in its setter (thereby passing responsibility to check the age to a method that can act upon issues) and then the setter can set age if it's returned valid ?
I think putting things like a checkAge() method in other places than the class would just be low cohesion and higher coupling?

The thing about maintenance/ boiler plate i dont really get 😄?
As i understand it, boilerplate is when the same code is written in more areas/classes, and the get/set method is written exactly the amount of times in a class that a property is, also, maintining the get/set in a method or a property should result in the same amount of maintenence work inside the {} as the functionality should be the same either way it was written? 😄

My question is then just - why properties over getter/setter methods when the only thing you gain is binding and pretty code?
Ofc. I cant get around using properties when binding, but else...
The action would be the same wether i set in a method or property, but in the method i can inform myself of the operation and wont get silent failure like the set age example, and maintaining a getter/setter method is IMO same work as a property, they'd have the same lines of code inside the {} either way..

I seriously asked all my teachers about this, and none of them could argue for the use of properties, once its set up like that, other than saying thats what people do, and it looks better 🤔 which IMO isnt a good enough answer... So sorry if i am pushing you here mate, but im just trying to understand why everyone, every video, tutorial and teachers says that i should be using the properties outside binding 😅

@gronostaj i dont think we'r quite on the same page, im well aware of how the getter/setter methods work, my issue is coming to C# from Java and understanding why everyone want's to use properties...

This is the showdown im concluding after my research on general guidelines and best practices :

Properties vs getter setter methods:
1 binding. 0
1 Setting 1
1 getting 1
0 inform/act on fail-success 1
0 computations 1
0 error on invalid set. 1

Im aware properties can do informs and stuff by throwing exceptions, but ive found most people frown upon throwing exceptions from properties(then it should be a method)

(Continued)

@Ranchonyx well from that viewpoint i definitly agree, i find it's picked up so quick, and alot are just like java ☕

@Ranchonyx microsoft java 🤔? Must be a programming joke i havent heard yet? 😅

@gronostaj, so, if understand you correct.. you'd say that once a setter does more than a 'this.age = age'
Or a getter 'return this.age' we should opt to do the validation/computation of the age in a seperate method that then use property setter once age validation is done ?

So if this was a person class.
We could have following:

Public void validateAge(int age)
{
If (age>5)
{
This.age = age
}
Else
{
//Handle if age to low
}
}

@gronostaj

But why use the properties if theres a chance down the road it would need to be a method, and there's no advantage other than being pretty...

thats the thing i dont get, im aware that once we'r talking bindings thats where properties come in

but otherwise - again IMO - i merely see properties as pretty getter/setter methods, that can't notify the program/user of successfull or failed set action, unless you start throwing exceptions - which as ive read in the books and seen around that throwing exceptions from the setter of a property is generally frowned upon ?

Asked my teacher this and he couldn't answer me why i should then use properties over getter/setter methods unless we'r talking bindings, and he's a strong advocate of properties, but had to recognise that you could end up making a setter in a property that didnt actually set a value, and it wouldnt get notified unless exception thrown which he wouldnt do, or you check the field afterwards if it changed 😅

@electrineer lol 😂

@RememberMe so im pretty comfortable with intellij as we use that in class, but what would you do for GUI in the app?