Alessandro Puzielli

Hi,

my mail is a3puzielli@gmail.com..

Thank you very much

Hi Samarpit, thank you for your article. I have been studying the microservices with Spring Boot for some days ago and your article is clearifing me some details of the topic better the official tutorial of Spring.io. Can I you ask the source code, please? I don't work with STS but directly in Eclipse vanilla.

Thank you for the article: I followed it for my first upload in pypi and the process is ended succesfully (After a renaming for a homonym project). Thank you!

Hi,

I have 2 questions:

1) When you select all users, why does you use the signature public Set getAllUsers(int id)? Into code, the id is'nt read, then it's useless. Is'nt better to use Set getAllUsers()?

2) Into login's situation, If I need to trim the name and password, it's better to trim them before calling the method of login or inside the login's method?

Bye

Alessandro

Software engineering has more standards for visualization. For example:

1. UML
   
2. SysML

These modelization languages can express the same level of precision of traditional engineering's models, but they require time and effort.

If I want a not-formalized sketch, useful only to understand the general idea, in software engineering you can use the showed diagrams. In the same way, in traditional engineering you can draw by hand.

The difference is that in tradtional engineering, the standards are necessary for development and delivery of project because the product require more business lines with a common language.

IMO, in software engineering the constraints of process are more relaxed.

Software engineering has more standards for visualization. For example:

1. UML
   
2. SysML

These modelization languages can express the same level of precision of traditional engineering's models, but they require time and effort.

If I want a not-formalized sketch, useful only to understand the general idea, in software engineering you can use the showed diagrams. In the same way, in traditional engineering you can draw by hand.

The difference is that in tradtional engineering, the standards are necessary for development and delivery of project because the product require more business lines with a common language.

IMO, in software engineering the constraints of process are more relaxed.

The snippets remember me the Strategy design pattern..

The snippets remember me the Strategy design pattern..

Hi john,

I lose a step: in the method Car.sava(Car car) there's a connection to DB and you says that the DB is unaviable.

Then in the DAO I need a connection to DB (the method saveCar(Car car) call this method without other elaboration).

When in test this instruction runs:

verify(mockDao, times(10)).saveCar(refEq(aToyotaPrius, "serialNumber"));

you might to receive a PersistentException (or SQLException) in testing time and you can't read the value of assertion.

How do you can testing the method save if you don't modify its code?

Do you use any framework? In the article there's mention.

Thanks

Hi john,

I lose a step: in the method Car.sava(Car car) there's a connection to DB and you says that the DB is unaviable.

Then in the DAO I need a connection to DB (the method saveCar(Car car) call this method without other elaboration).

When in test this instruction runs:

verify(mockDao, times(10)).saveCar(refEq(aToyotaPrius, "serialNumber"));

you might to receive a PersistentException (or SQLException) in testing time and you can't read the value of assertion.

How do you can testing the method save if you don't modify its code?

Do you use any framework? In the article there's mention.

Thanks

Hi Adam,

In my opinion the interface is matter for the maintenance and the evolution of the software: it's an indication, a landmark about the interanl stucture of the program (the concept of program to the interface not to the implementation quoted by Santini).

For example you have the code

ServiceIF service = new Service();

and you prefer to re-write as

 Service service = new Service(); 

( Service is a concrete class and ServiceIF is an interface)

Later, the customer ask you to extend the function of a software component.

The solution iscreate a new class NewService (horrible name but it's an example :)) sharing the public behaviour of Service.

With the first solution, you can write

 public class NewService implements ServiceIF//bla bla

with the other solution

 public class NewService

and you must be more careful for the regression test.

At the least, I think the the interface implemented by one class is an assurance for the future ;)

The bad practise, IMOH, is to use name as

ServiceIf, IService, ServiceInterface

instead a name closer to functional world.

Bye

Alessandro

Hi Adam,

In my opinion the interface is matter for the maintenance and the evolution of the software: it's an indication, a landmark about the interanl stucture of the program (the concept of program to the interface not to the implementation quoted by Santini).

For example you have the code

ServiceIF service = new Service();

and you prefer to re-write as

 Service service = new Service(); 

( Service is a concrete class and ServiceIF is an interface)

Later, the customer ask you to extend the function of a software component.

The solution iscreate a new class NewService (horrible name but it's an example :)) sharing the public behaviour of Service.

With the first solution, you can write

 public class NewService implements ServiceIF//bla bla

with the other solution

 public class NewService

and you must be more careful for the regression test.

At the least, I think the the interface implemented by one class is an assurance for the future ;)

The bad practise, IMOH, is to use name as

ServiceIf, IService, ServiceInterface

instead a name closer to functional world.

Bye

Alessandro

Remember the API all of the all the language is my problem too: for this I decide to learing Scala, because this language uses the Java bytecode in correct way (and vice versa).

Happy coding!

Remember the API all of the all the language is my problem too: for this I decide to learing Scala, because this language uses the Java bytecode in correct way (and vice versa).

Happy coding!

The problem is'nt a NEW or OLD Build server.

The problems is to have A BUILD SERVER!

:)

The problem is'nt a NEW or OLD Build server.

The problems is to have A BUILD SERVER!

:)

I don't understand:

1) I code static method for general and common function: formatting a

java.sql.Date

for JSP page, compare two class, validatio, mathematical need.

2)for debug: i code static the number of object of a class

You says that is diffucult for the testing? I say that the static methods must not be necessary for the business logic but only for the secondary aspects. Do you prefer - by default - testing ALL the functions or only the new functions whenyou must deploy a new feature of your software?

I don't understand:

1) I code static method for general and common function: formatting a

java.sql.Date

for JSP page, compare two class, validatio, mathematical need.

2)for debug: i code static the number of object of a class

You says that is diffucult for the testing? I say that the static methods must not be necessary for the business logic but only for the secondary aspects. Do you prefer - by default - testing ALL the functions or only the new functions whenyou must deploy a new feature of your software?

RIP..

I began programming with the JDK1.4 for work.

the question is:How much MANAGERS/CUSTOMERS know about this event?

RIP..

I began programming with the JDK1.4 for work.

the question is:How much MANAGERS/CUSTOMERS know about this event?

Great post!

A question: in your opinion, why the developer not send any message to user?

Why often dont' they write the correct message in the logs but they prefer a general

logger.error(e);

instead a more specific

logger.error("Error in nameMethod in {I/O,SQL, BLAH BLAH}",e);

?

Great post!

A question: in your opinion, why the developer not send any message to user?

Why often dont' they write the correct message in the logs but they prefer a general

logger.error(e);

instead a more specific

logger.error("Error in nameMethod in {I/O,SQL, BLAH BLAH}",e);

?

Important subject!

Generally I prefer the hard copy: I download from Internet the technical articles and books that I read as reference ( i.e. "Thinkin in Java" of Bruce Eckel). Also I don't buy book about programming language but about algoritms, data structure, architecture (i.e. the Tanenbaum's book about network systems, operating systems etc) because I have found often that the programming books are full of code, then it's better to coding directly :)

PS I try ever to buy the books not in english but in italian language :))))

Important subject!

Generally I prefer the hard copy: I download from Internet the technical articles and books that I read as reference ( i.e. "Thinkin in Java" of Bruce Eckel). Also I don't buy book about programming language but about algoritms, data structure, architecture (i.e. the Tanenbaum's book about network systems, operating systems etc) because I have found often that the programming books are full of code, then it's better to coding directly :)

PS I try ever to buy the books not in english but in italian language :))))

Hi!

A only warning: the links are bad written.

In the article the link to tool is http://java.dzone.com/www.panopticode.org/, but really it's http://www.panopticode.org/.

I have a doubt: How often do you use the code metrics? I'm a joung software engineer but I don't know if it's more their effective use at work.

Bye

Hi!

A only warning: the links are bad written.

In the article the link to tool is http://java.dzone.com/www.panopticode.org/, but really it's http://www.panopticode.org/.

I have a doubt: How often do you use the code metrics? I'm a joung software engineer but I don't know if it's more their effective use at work.

Bye