#Common Quantifable Outcomes

1 messages ยท Page 1 of 1 (latest)

minor charmBOT
#

<@&1004656351647117403> please have a look, thanks.

#

Here is an AI assisted attempt to answer your question ๐Ÿค–. Maybe it helps! In any case, a human is on the way ๐Ÿ‘. To continue talking to the AI, you can use </chatgpt:1108714622413963314>.

#
TJ-Bot
Hello everyone. In general, what are some omnipresent quantifable outcomes that most Spring Web MVC developers are able to accomplish throughout their careers? If you feel that the scope of this question is too limited to Spring Web MVC, please extend it

you have mastered Spring Web MVC, some quantifiable outcomes you may achieve include:

  1. Building robust web applications: As a Spring Web MVC developer, you should be able to create scalable and reliable web applications that meet the needs of your clients or users.

  2. Implementing RESTful APIs: Another key outcome is the ability to design and implement RESTful APIs using Spring Web MVC, allowing for seamless communication between different systems.

  3. Integrating with databases: You should be proficient in integrating your web applications with databases using technologies like Hibernate or JPA, ensuring efficient data storage and retrieval.

  4. Implementing security measures: It is essential for developers to be able to implement security features such as authentication and authorization in their Spring Web MVC applications to protect sensitive data.

  5. Optimizing performance: A skilled developer can optimize the performance of their web applications by implementing caching mechanisms, tuning database queries, and minimizing load times.

Overall, mastering these outcomes can lead to a successful career as a Spring Web MVC developer, demonstrating your expertise in building high-quality web applications that meet industry standards.

hot dune
#

Common Quantifable Outcomes

iron flame
#

its not about "extending it to Spring". its that you arent asking any specific question. you're asking

when using Spring MVC, what experiences have you had?

#

which boils down into "is Spring MVC useful? can you quantify it?"

#

its broad, and its opinion based

#

we've seen Spring MVC work on the field

#

so whats your real question?

#

basically asking "why use Spring MVC?"

#

it solved problems

#

had some task, had to choose which tool to use, Spring MVC worked

#

seems like you're asking "whats the purpose of Spring MVC", or "how does Spring MVC compare to ..." (without specifying the ...)

#

if you want to see Spring MVC at play, theres tons of examples

#

do you think it doesnt work? if so, ask about that

#

gotta be more specific

#

its broad, as in you arent asking about anything specific about MVC, just asking "is it good" basically

#

you are literally asking that

#

"what value does Spring MVC have"

#

yeah, but how can you deny that you arent asking about the purpose of MVC, whether its a good fit?

#

you wanna see it in action

#

no?

#

you wanna see where it shines

#

exactly, "how useful is this tool"

#

there are tons of examples online. going for personal experiences? youll get different answers

#

cause every experiences it differently

#

best to look towards where its used in high-traffic systems. you're just asking for personal preferences

#

ive done nothing. the times ive had to work with it, i just used it as it was meant to be used, and it worked

#

i didnt try putting it on some pedestal. its a tool, like a screwdriver

#

its like asking "what ways has a screwdriver improved your productivity?"

#

it does what it was designed to do. are there better tools? thats a different question

#

yeah, tons of businesses use it, and it works for them

#

thats where caching plays a role

#

you cant determine what a user wants when they havent interacted with the system yet

#

so all you can do is try to cache what has been proven by other users, and provide that pre-processed data to new users

#

are you asking if Spring MVC tackles the problem of FID?

#

first input rarely matters

#

if users are straying away from your app cause the first interaction takes more than 100ms, your app aint providing a service they really care about

#

optimizations are based on heuristics. and those heuristics can only be obtained after usage

#

depends on the app, the throughput

#

i mean, its possible. but you also have MVC apps with 2 second response times

#

because the implementation was poor

#

which is equivalent to using a screwdriver properly, VS not using it properly

#

load balancing is a thing

#

if theres high throughput, it could put load on the balancers, causing them to perform less

#

which results in either slower response times, or data that isnt "up to date"

#

it really seems like you're questioning the performance integrity of Spring MVC

#

throughput can cause congestion, which can lead to slower reponse times

#

they usually go hand in hand, yeah

#

it depends on what system they were using before

#

i mean, if some inexperienced dev wrote the system from scratch, theres a good chance using MVC will improve performance, since it's maintained by experienced devs

#

but MVC isnt just one thing. seems like you are more focused on the data sector

#

queries

#

it depends on the system they're working on. if they're working on a highly optimized system, then no

#

"how can we get better than the best?"

#

thats the million dollar question

#

and thats where you start looking towards the well-known projects which make use of it

#

thats the route to go

#

even though people have used Spring MVC here, you dont know their story. youll get different answers from different people

#

so its best to look at where it has worked in high-traffic areas

#

you can get opinions here, but with how broad the question is, could range from "it sucks, dont use it" to "its the best"

#

instead, look at some of the big-time open source projects, see how it plays a role

#

maybe mimick it, perform some benchmarks to see if the same works for your environment

wicked bough
#

How can Spring MVC relate to the performance improvement topic? I think it's a just web framework that has nothing to do with performance.

And I don't think a junior developer really have a lot opportunities to work on performance related tasks

#

Just stop thinking this way. You as a junior developer is supposed to write business logic, meaning to implement features. If your task is really improving performance you simply won't think Spring MVC has anything to do with performance.

And stop thinking you have to put so called metrics on your resume, out of nowhere

That would not only make your resume look unreal, but also look like you blindly copied the text from chatGPT

And in a workplace performance will only be improved when you have to. Meaning 99% of time there's no need to improve performance.

wicked bough
#

Imagine Im a professional F-1 race car driver. Now on my resume I wrote "optimized the engine design and improved the gas efficiency by 10%". Hell no I am a driver not a machenical engineer! This is what it looks when people put unrelated metrics on resumes out of nowhere, no matter what the title is.

And this 10% is non sense because improving engine efficiency by 10% takes decades or even generations of research by the whole industry. However I claim I accomplished this all by myself as a side hobby and it took one year.

#

Think about it. How do you answer this quick interview question:

You have a Spring MVC application and it's running slow. How would you improve the performance?

candid carbon
wicked bough
candid carbon
#

The way the image is build & what's included, when & which beans are initialized, etc..

#

For example I can build the same spring cloud function with a massive difference in startup time.

wicked bough
candid carbon
#

There are many techniques.

tight umbra
#

why would u want to delete a thread. that just hurts anyone else who wants to read upon it and learn

#

not sure i follow

#

u created a thread bc u had a question and now, a day later, u feel embarrassed about it or what?

tight umbra
#

unfortunate. but perhaps others may gain sth from it. so lets keep it up ๐Ÿ™‚

candid carbon
#

In which regards? Why hide information from others?

#

How so? You post it on a public server?

#

By that reasoning you wouldn't be allowed to use our responses as they're our private property?

#

That's not how free, public support works. If you want such a thing you'll need to look into paid support.

#

Technically the server owner I guess.

#

Doing so is pretty poor form and will limit the people that are inclined to answer in the future.

#

Part of our help is that it's also for others with the same issue.

#

It's like a forum with deleted topic starts, it hollows things out.

#

But feel free to try #server-suggestions .

wicked bough
#

You are able to delete all your own msg I think

acoustic chasm
#

You can't do that
You still have to follow the server rules, and what about other people messages ?
Why would you be able to control what other can do, but not other ?
You are asking to have privileges but not other
Sure that's your thread, but other are still posting on it, and so they expect that their messages are their and not controlled by you

iron flame
#

but if you deleted the thread, you'd also be deleting the contributions made to it

candid carbon
final sundial
#

It's my opinion (and just my opinion, this is not a mod-statement), that the noise of such threads would be distracting.

I would anticipate that that the majority of regular helpers would not engage in these threads. As a volunteer, I would prefer a chance to help people en masse, rather than at most one - it's just not efficient use of effort, because there always more supplicants than supporters.

candid carbon
#

Anyway this is no longer related ot the original question, further discussion belongs in #server-suggestions .

final sundial
#

A good reason not to be able to delete the original question.

candid carbon
#

For reference @hot dune initially asked:

Hello everyone.

I was wondering what are some effective strategy/tools you would recommend for reducing first input delay in a Spring Web MVC application?

First input delay is the time between a user's first interaction with a webpage (e.g., clicking a button or link) and the moment the browser can start processing that interaction.

minor charmBOT
#

@hot dune

Your question has been closed due to inactivity.

If it was not resolved yet, feel free to just post a message below
to reopen it, or create a new thread.

Note that usually the reason for nobody calling back is that your
question may have been not well asked and hence no one felt confident
enough answering.

When you reopen the thread, try to use your time to improve the quality
of the question by elaborating, providing details, context, all relevant code
snippets, any errors you are getting, concrete examples and perhaps also some
screenshots. Share your attempt, explain the expected results and compare
them to the current results.

Also try to make the information easily accessible by sharing code
or assignment descriptions directly on Discord, not behind a link or
PDF-file; provide some guidance for long code snippets and ensure
the code is well formatted and has syntax highlighting. Kindly read through
https://stackoverflow.com/help/how-to-ask for more.

With enough info, someone knows the answer for sure ๐Ÿ‘