1,365 reputation
514
bio website workplace.stackexchange.com/…
location Midwest USA
age 26
visits member for 2 years, 3 months
seen 19 hours ago

Hello world!

Engineer by day.... engineer by night?


Jul
24
comment Programming Interview
@CsBalazsHungary - This question is not a good fit on Workplace as is currently (nor any Stack Exchange site).
Jul
24
awarded  Good Answer
Jul
23
comment How should I remember what I was doing and why on a project 3 months back?
@BTownTKD I say that in my answer :)
Jul
23
comment How should I remember what I was doing and why on a project 3 months back?
@TheIndependentAquarius likely because generally comments are intended to be more or less post-its/stickies. The way Stack Exchange has things setup to say, "this answer was great" is either upvoting or accepting an answer. Comments here are not necessarily intended to last.
Jul
22
comment How should I remember what I was doing and why on a project 3 months back?
@TheIndependentAquarius no problem, glad it was helpful. That situation can be overwhelming.
Jul
22
awarded  Nice Answer
Jul
22
revised How should I remember what I was doing and why on a project 3 months back?
added 58 characters in body
Jul
22
revised How should I remember what I was doing and why on a project 3 months back?
added 58 characters in body
Jul
22
answered How should I remember what I was doing and why on a project 3 months back?
Jul
22
comment How does your career proceed after you do certification in SAP ABAP?
Why was my question closed as off topic?
Jul
15
answered Is it true: use Agile methodology results less planning?
Jun
24
comment How to handle vague requirements and a manager who needs continuous output?
You are basically asking, "how should projects be run from a project management perspective?" which is a really, REALLY broad question.
Jun
20
awarded  Good Answer
Jun
18
comment How much information about an error should be shown to the user?
Second, you grossly overestimate average user ability to self-resolve problems. The overwhelming majority of the population is what most developers/programmers/Stack Exchange folks would call computer illiterate. Most of these people quite frankly are not equipped to diagnose, troubleshoot, and resolve problems. Detail can actually make things worse because people can misinterpret things which would make complete sense to developers. Programmers and tech savvy people are almost universally not the target demographic for most applications, much to the disappointment of everyone here... :)
Jun
18
comment How much information about an error should be shown to the user?
@JonBentley a few points for consideration. First, the primary point of this answer is you give the user actionable information. If it's an error they can fix need to tell them information to resolve it. This falls into You show the user what is actionable for them. If you know the cause of the problem, then you show that to the user in the description. But generally if you know the reason for an error you will know the problem resolution to inform the user appropriately.
Jun
17
awarded  Nice Answer
Jun
17
revised How much information about an error should be shown to the user?
added 87 characters in body
Jun
17
answered How much information about an error should be shown to the user?
Jun
9
revised Improving the running time of Breadth First Search and Adjacency List creation
formatted code better
Jun
9
suggested suggested edit on Improving the running time of Breadth First Search and Adjacency List creation