martinobettucci

<?php

class MatrixMath {
    public static function dotVectors($vector1, $vector2)
    {
        $total = 0;
        $dim = count($vector1);
        for ($i = 0; $i < $dim; $i++) {
            $total += $vector1[$i] * $vector2[$i];
        }

martinobettucci

<?php

require __DIR__ . '/../vendor/autoload.php';

use Phacterl\Runtime\Scheduler;
use Phacterl\Actor\Actor;
use Phacterl\Message\Message;

// Le puppet master
$scheduler = new Scheduler();

martinobettucci

from ledgerblue.comm import getDongle, CommException
import asyncio
import websockets
import json
import binascii

dongle = None

async def hidProxy(websocket, path):
	global dongle

martinobettucci

THE TAO OF THE AGILE SOFTWARE CONTRIBUTOR

• I look into my dashboard to see what's pending from my team between each resolved issue.
• I should be aware that issues pending feedback are not only standing-by tickets but people and I assure them all my efforts to let them move forward.
• I should take my next ticket from the current sprint pool and from the out of sprint pool in this order.
• Priority should be my best concern, I should take tasks based on their priority from critical, major, medium, minor and trivial in this order.
• Blocker priority should be taken instantly regardless of their positioning.
• As soon as I decide to be in charge of an issue, I should assign that to me as to notify my peers that I will handle and take care of that.
• As soon as I take an issue in charge, I will plan a discussion with the reporter to share knowledge and our point of views.
• When I finally start my meeting or my developments, I put the issue in DEVELOPMENT as to notify my line managers I started looking/wor

martinobettucci

PLEASE DO NOT USE A PUBLIC SPACE OF A TEAM CHANNEL TO DISCUSS ANYTHING PUBLICLY!

If you join a team channel, use only to plan meetings with (someone from) the team or discuss any specific topic in a clean way as stated here.

In order to keep the common place as clean and organized as possible, use the following formulas to discuss issues with the team channel members:

• Always @quote the user(s) you are referring to.
• Always link what are you referring to (do not just copy the issue name) because it saves times for everybody to reach the item you are about to discuss.
• Put your questions and your arguments into a thread to keep the common plaza nice and clean.
• By doing so, only interested user by the subject will participate to the spawn thread while other posts of the day won't get lost.

martinobettucci

You do not feel comfortable to write specifications from ground up, I understand that.

In the near futures, you will receive only slightly detailed specs and you will be asked to give feedback and advices to story owners to help them improve theirs documents effectiveness instead. Please, use the skills of yours as a technical expert to tell the story owner (once you have a clear view of the intentions) if you have a better idea: do not hesitate to disagree and say why.

You are engineers, you should give your expert point of view when interacting with someone!

martinobettucci

You already do a great job about setting into DEVELOPMENT status the tasks as soon as you start investigating, thanks! Thanks also for submitting optional fields like "Reproduced" or by writing a comment when it involves any bugs. This gives me great visibility about the achieved job!!

I'm asking to you to help me improve my overview about pending job: in order to not overwhelming you all with too much documentation work, I'm requiring to all of you once leaving the day with a pending task to write a comment including your current day findings: this could be anything, even "I just started looking around", "Need to talk to Martino", "I reproduced but still not understood why it happens", "I think this is related to the XXX or the user model but I'm unsure” ... it does not care if you write good or wrong statements, just write down the current end of day status of your findings.

This way I will be able to anticipate actions for the further comings and I will have an easier reporting end of day to businesses

martinobettucci

public static String checkNull(String value) {
	if (value == null)
            return null;
	return value == null ? null : value;
}

martinobettucci

Can you speak English, French? Examples

What positions have you covered so far? Single developer, leader dev, technician, etc..
When have you received your firts and last high degree (bts in 2000, master 2008, par example)

Explain to me how do you see yourself as a employee and as a tech guy.
Tell me what people have told you about yourself as an employee and as collegue.

What is making you like your job and why you keep working in this industry?

martinobettucci

Open (Default)
  Issue is open and waiting for a resolution
Fixed
  A fix for this issue is pushed into VSC into the tree and qualified.
Won't Fix
  The problem described is an issue which will never be fixed: reason must be provided.
Duplicate
  The problem is a duplicate of an existing issue: link must be provided.
Incomplete
  The problem is not completely described: specify required informations and notify the person(s) in charge of complete them.