dnl_pozzobon

As an Italian I have really mixed feelings about this. When you hear people speaking on TV they mix-in so may English words that at times it becomes difficult to understand what they are saying. People forget or don't ever learn the Italian words for simple things like `spelling` and `to set`.

> requires anyone who holds an office in public administration to have “written and oral knowledge and mastery of the Italian language.” This might be useful, but it will be applied badly (as they do) so you get people that don't intermingle English words but the speak only in the local dialect or with an accent so thick that they might as well be speaking another language.

> It also prohibits use of English in official documentation, including “acronyms and names” of job roles in companies operating in the country.

I don't have great feeling about this as we have words that are correctly taken from another language because they did not had a counter part (mouse for example) so this will breed horrible new Italian versions of the English words: we will have to work with a "computatore" (remember nobody will remember that "calcolatore" already exists) and a "topo".

> Under the proposed law, the Culture Ministry would establish a committee whose remit would include “correct use of the Italian language and its pronunciation” in schools, media, commerce and advertising. The sentiment is good, the Italian language is a beautiful language, we need to learn to speak it correctly and help it evolve naturally, but I feel the approach is wrong and reminds me of a similar thing that the goverment did during the fascist regime where people where forced to even change their name because it sounded too foreign...

I tested it and it's quite impressive

i got a suggestion for your project. Instead of clicking a team member to make it work on a task, what if you have to manage the size and priorities of the lanes, and the other aspects of your production. the biggest problem that i see now is that you have to do 2 kinds of managment, making people work, and making the flow of work effective. by eliminating the first one you are simulating a little better how a dev shop should work. with this approach your devs would work on the projects based on their priority, but would stop if there too much stuff queued in test, the founder would be finding new projecst only if there's enought capacity for the devs , if not it can concentrate on other tasks. Late projects will cost you money so it doesn't make sense to have them in queue. you could also add that the team member time can cost you money.

I'm slightly bothered by the "reverse-interview" concept. To me interviews should be bidirectional you are there to find out about the company as much as they are there to find out about you. It should be treated as the starting phases of a negotiation where you gain information about the value of the asset you are going to acquire.

I'm certainly happy that viraptor shared this valuable resource, don't get me wrong, every little step in the right direction is a good thing. I simply would have liked it to have a better name in order to convey a different message.

right now i'm just collecting them from twitter, after collecting the link from twitter i try to find closing date and location, then I use an implementation of the Open Text Summarizer algorithm to find keywords to help the search functionality. the idea of letting users suggest information it's really helpful, thank you

what technology stack are you working on?