@true-dev001 thats how it should be ^^

Sounds like a significant improvement in management :)

I believe the manger / project lead is responsible for the project success.

The job of this person is to split/organize work in small chunks (for the devs).

.. and from my experience another MAIN responsiblity from management is to be a stress stopper!

E.g. customers are unhappy and pressure the company to produce faster.

Then a good management will not forward this stress to development/programming.

(To communicate the problems is an okay part, but distinct from forwarding stress)

And it seems your new management is way better in reducing (external) stress on you/ dev team

Happy for you :)

@ctnqhk I am no designer and I do not know much about design

I really wonder in which field such a UI is common

(Implicitly I expect, that nobody would a priori believe such a design should be adapted; comming from separated pages for sign up and login)

@ctnqhk o_O

I, I am astonished.

@ctnqhk

Oh man, those layer 8 problems ^^

I feel you

-> maybe a careful change in the UI could help to distinguish

(e.g. a popup/other ui-addition that hints: you made three invalid logins, maybe try the NEW social login)

.. but users can not be helped sometimes :/

I do not know, if I totaly miss how social logins work:
from my experience you talk about single-sign-on in the end:
- the authority is the social network
- no login will happen on your side
- your website will forward your user with a challenge/nonce to the social network login/site
- this side will do validation with the user and then forwards back to your side *(with a authentication token that encrypts the challenge/nonce and informs your website authority about the fact 'user authenticated on our side and is who he says he is'
- then you give the user your token

In the end everbody was happy and no password *field* was needed

Am I mistaken in some way?

@TheCommoner282

I have to add to this:

In my opinion is diligence a quality that differs a junior from a senior developer.

.. or at least should:

those non technical abilities like refactoring, if needed (and not developing the next feature) is strongly undervalued and not talked about.

I believe you get payed to say no, I am not yet finished with feature A (as functionality is there, but code is a total mess) and clean up first before moving on.

.. Product Owners / Managment mostly will not have the ability to evaluate the need for refactoring and needs to be restrained in their feature famine!

Problem: value of this only shows in the long time and therefore will not be visible in many cases

I changed, because I could not stand the feature programming anymore.

Always the same 'shit'

Knowing which classes, functions structure I will be building in the following week was toke the fun out of it.

But as of now I miss the fast feedback from coding ^^

Student in Computer Science Master :D

I now work as an auxiliary scientist in a reasearch project.

(during the bachelors I financed myself through work in a company as a software engineer)

Some ideas take long until they are adapted:

e.g. I/O:

input through hand/finger gestures in three-dimensional space is a thing I see in youtube videos from time to time, and there are first products too, but it is not adapted yet.

Output:

virtual reality and augumented reality is another possible vector for revolution: instead of the need of bigger TV's or screens this could be virtualized.

Existent revolutions are all the "cryptocurrencies" (e.g. Bitcoin, Montero, etc.) that really changed the world.

I believe it was 2% of the WORLDS electricity use that is spend on mining (!)

And wait for quanten computation; this might need a decade before it really arrives, but there are so many things in development :)

Agile was introduced with 'senior professionals'

.. in the founding times of computer science.

(e.g. a professional software engineer had a background in physics math or another field.)

If such a person commited to a deadline a whole lot of experience and knowledge was behind this commitment.

If you try to do push people with a lose focus and not enough experience (e.g. about hidden costs as increased maintenance through missing tests) to use agile, they will not be able to achieve the desired results.

I believe the main requirement for working agile is, that the team is able

- to act responsible

- manage time (e.g. the same job a management would do)

- deliver quality work/software (= giving space to non-functional requirements beside new features)

I understand the subtext of this post to question (unit) testing.

My two cents:
spending time (& resources & money) for test definition is useful, if the software needs to be maintained and will be evolved (or just developed further).

Those are just signs of a company culture with some problems ..

@meowlikethunder I know what will be behind this link without clicking it ^^

I feel with you!

... but this is (probably) not limited to computer scientists :)

@Numinex happy to help :)

development never ends ;)

@devnope

I have to note this one!

I know that feel soo good

but I have the feeling a lot of energy is drained after work,
for some of the people here 8 hours seems to little, but for me it is quite a lot..

dont be so overbearing, I do not know what level of education you are currently working on!

... and things like binary codes are it knowledge you do not have from school

-> only if you do stuff in private, as you are unchallenged in school

take an used business one with a dockingport.

I can not really believe that you prefer to work with 13' instead of a "real" workplace with 2 monitors and a decent keyboard :)

or maybe a kdeBook - if that is your final distro

@KillerHam

welcome to devRant :D

first ++ <3

@inukinator @killerham

do you hear about "Domain Language"?

-> it seems to be in use here, as it can be confusing if you have to translate from tech language to product owner language each time you speak to the product owner.
And it can produce misunderstanding as well, if the translation is bad

---

and I am for myself not sure if it is good or bad :)

@maven ahh :D

quick lookup on wikipedia helps

... and now I cant stop thinking about pie for breakfast %)
jamjam

@Orionss I do work with c#. we use gulp to host the api-Backend.

So I can ensure you that you do not have to use IIS or Azure.
-> there should be even more ways, google is your friend :)

welcome to devrant! :)

pardon, but I have to ask what your "Pi" is ^^

right now I can only think about Raspberry Pi, and that does not fit :D

@SubhrajyotiSen

I get goosebumps :D

@Orionss hmm, I dont get the point

"little things" like whatsapp are not that small

-> and if you talk about startups, they will use whatever they know. They wont hire seniors explicit for c#

how long is his/her name? :D

@codepoet

my personal favorite is, if the password is shortened in be!

e.g. limit is 16 characters and you enter 20! HATE

@Orionss define what "innovation - related projects" are for e.g.