Isammoc

As any subject to learn, you don't have to if you don't want to.

More seriously, as in programmation, many new languages manage memory with a garbage collector or other mechanisms, but if you want to be a good developer, you need to know how all this is done underneath.

To drive a car, you don't need to know how an engine works, but to create one...

And for the particular subject, you have to understand the principles under your tools to know how to change parameters and understand why the tools can be biased with bad parameters (or not enough data).

I move from angular 4 to react TS for my side projects. Mostly because of the main philosophy (components vs functional, my back-end is in scala) but for using redux as well. The capacity to replay user behavior is a killer feature. And a well designed tools enable a development velocity I didn't have with angular.

Behavior, data, domain, hierarchic, are other words to put before driven development

The whole topic is mainly discussed over the web. But I always have the same questions:

* How explain the value to managers and/or direction to add a step when the code review is not present in the company?

* How to enforce the process inside a team? What to do in front of a developer who do not want to change his/her code after a code review?

* When do you put the line between immediate correction or new ticket when code reviewing?

Errr... tricky question. It depends on many things.

Where is this name used?

* API: vendor_id * HTML attribute: vendor-id * other variable: vendorId * other type: VendorId

Id for Identifier but ID for Internal Distinction :P

As usual, there are many obvious question (and some less obvious ones):

- How often do you change the available cars?

- Is there a registration for something? (newsletter apart, can your users save a car for later?)

- who will do the actual modifications? How easy for this person to change what (s)he has to change?

- From where do you perform the modifications?

Yes, I was asked to create a missile guidage from an helicopter, and I refuse, I know somebody else made it now, but I didn't want to participate into that. In another subject, I refuse to develop a password rule : for log in, the password would be case insensitive, but will be case sensitive for unsubscribing. It was unfair and against all security.

Once you edit the file (left panel), you can still click on left item "+" signs, it disappears, but nothing is added to the file (left panel).

1. Good idea

2. I tried a little, and once you edit the file, the right items didn't work anymore :'(

As a side project / alone or in an organisation? I assimilate the former as theory, usually your work in this sort of project was not challenged by your pair. In an organisation, your work has been reviewed, challenged and you had gain real experience from that.

I don't know how to categorize the next case: A group side project. The work is challenged, but it is difficult to prove.

What about DistinctMyName? JobMyName? KindMyName? CruelMyName? Simply choose an adjective, perhaps a location, something to distinct you from the other homonyms.

IMHO, Junior developer or junior whatever means that the person has little to none experience in the field. That doesn't mean that this person has no knowledge.

Personnally, I see a Junior whatever as someone who has some theoric knowledge about the whatever but did not have the time to apply it yet.

Not even an archive? Nor a sample? No confidentiality? In my mind, it is just another mail stealing site.

In my own experience, bootcamps or other made up stages are about to fail because of the fact they have prerequisites that are not shown.

For your friend (and you), I will recommend to start with basic knowledge. What is Boole's logic? What is a microship? How to control a microship.

An example will be : http://www.nand2tetris.org/

Begin with a (only one) project will fall in some pitfalls: - do not cover basic principles - assume to know a framework, or to use bad practices - do not teach programming, but a language for only one purpose

(sorry for my bad english)

Not a new idea, many had it before. Nonetheless, it is intellectually interesting, but not practically.

1. Those early users would come for "free" money but how do you shares those shares? Equally by user? by feedback? ponderation by value of the feedback? How do you value it?

2. Those early users will sell those shares to who? Your company : Lowering the capital?

3. Don't you think that real early users would prefer to use your product for life instead of having some shares not really easy to fairly create nor to sell?

I have several personal CVs. All about nothing, I made an unique CV for each job description I'm into. Only to try to fit as close as possible what I figure they want (no cheating, only highlighting what is more interesting for them).

But only when I personnaly ask for a job.

On contrary, when they come to me, I refuse to give other information other than publicly available : they are coming, I do not work for them yet.

* #regressions (bugs already seen, already fixed, but coming back) => should be zero (but sadly, not everywhere)

* Is she confident when there is a release ?

* If there is an API : #questions (by dev) not already answered in documentation

Many and many metrics points to add... But what's relevant is business dependent...

But to remember 6 random characters is awful, why not 3 words like this one : http://what3words.com/ Same problem, similar idea, another solution.

"how can you evaluate competence" => Do you really want to evaluate competence at this time? Or evaluate evolution of this competence? First is a comparison with others but you are unique in your team; second is a comparison with your past self, and this is easily achievable.

Hi. 1. Only for windows (I have only linux here); 2. From a not well known website; 3. no source. How to know it is not a virus ? A formatter which will erase all my pc and all my family's. Seriously, I will not download your game but I wish you lot of successes.

I've seen a website without password. To login: you have to fill you email adress, they send you an email with a one time auto login token.

It was great!

But (because, there is a "but") it was (I repeat) a one time auto login token.

If there was a for ever auto login token, this mail may be lost, duplicate, or worse, compromised.

The one time auto login is "secured" in the way you know you will have first access to this mail (mail is mostly unsafe) and the link worked.

Advantage : only one password (double authenticated for several providers) for your mail. As would be an oauth connection.

In a transactional mail ? Muh... "transactional" mean with an action, but commonly with a paid action, with private informations like a credit card number... I will not feel safe if in the same email I have a confirmation I have paid something (ie: advice about payment information are provided) and a link that allows the mail reader to get those informations.

There were my 2 cents.

Disclaimer : I am not a lawyer, I am only a developer, computer scientist and computers lovers :P

First of all, warn your users what you will store and for what purpose. Example : on your registration page

"Email are stored to identify you and to send notifications if you want to (configuration in your profile page). Password will be stored salted and encrypted, but don't forget to pick different ones for different sites. All personal informations that we store will only be used to our purpose and not selled anytime, ie not now neither ever."

Make clear your site is a side project, a beta, an alpha; that bugs may occur; that is possible to create apocalypse and kill kittens (cf disclaimer of VLC beta on Android).

More, if you keep private informations only to identify users, you can tell that all informations will be deleted (and you will) when your project will be full. (beta to production deletion).

Where are the graphes ? I only see trees...

Buggy quizzes and not accurate... :'(

No pricing, No information about privacy, No information about if this entirely online or you have to install something No real documentation before being registered

All of this => I won't register

Great idea ! But you are in front of lot of troubles :

* class are copyrighted to the teacher (or the school) in many crountries, you might have some law problems. * students are generally poor => free to use * students are genereally technology addict and know how to configure ads blockers. * be sponsored by universities

Ideas : * allow teacher to subscribe, and have a different interface to answer students' questions (students may discuss without teacher know, of course) * mobile app to study in transport * allow teacher to add optional exercice with correction (you do not want to be another online school and allows teacher grades their students)

One more : If I denied acces from facebook, I go to a page of your site which was broken....

Very nice looking... but what it really does ?

If I use the service, will I collect links for my purpose or yours ? What will I see (screenshots, demo page ?)

"My social accounts" (plural) but only Facebook ?

Links to other pages is really too small. Worst : No link to home page is clearly visible.

Why do you need my mail or my location ? (in Facebook permissions) please, explain why !

In "Legal", "INTELLECTUAL PROPERTY INFRINGEMENT", if I like or post about a website I don't own... I post a content that I am not owner... So I should not do it... I prefer not to use your site.

Hoping I helped

Like github pages ? http://pages.github.com/

Do you really want I send my friend address to a website ?

Some users already have difficulties with simple procedure and you want to complicate it. Without talking about issues with old "friend" who will hack you.

I think it is a good thing for an company intranet where you replace friends by collegues. But not for an end-user.