Experienced Devs

3956 readers

1 users here now

A community for discussion amongst professional software developers.

Posts should be relevant to those well into their careers.

For those looking to break into the industry, are hustling for their first job, or have just started their career and are looking for advice, check out:

Logo base by Delapouite under CC BY 3.0 with modifications to add a gradient

founded 1 year ago

MODERATORS

snowe@programming.dev

jmk1ng@programming.dev

drewsiferr@programming.dev

createOrUpdateMeeting() vs createMeeting(). Which one do you choose and why? (programming.dev)

submitted 1 year ago* (last edited 1 year ago) by JokersPistol@programming.dev to c/experienced_devs@programming.dev

12 comments fedilink hide all child comments

Which one is easier to develop and work with (which saves the most time)? Which one would you go for? The name of the API represents its true purpose in this case by the way, createOrUpdate creates or updates the passed in meeting and create just creates the meeting. I will be the only one working on this project for now, although obviously, I would like others to work on it with me eventually.

you are viewing a single comment's thread
view the rest of the comments

[–] sbv@sh.itjust.works 1 points 1 year ago

If the function is doing input validation, it might be cleaner to have a single code path for both creation and update. Especially if you eventually assemble an SQL statement that is INSERT OR UPDATE.