Too much lack of content paired with a not so skilled speaker made this talk too boring and embarrassing in some moments. Please get better demos next time and don't focus excessively on a specific technology if the talk is not meant to be
A lot more practical than the description made it out too be, imo it could've been explained better with a more "theoretical" approach. Some helpful pointers anyway, especially towards the end of the talk, e.g. take into consideration API versioning from the start
A lot more practical than the description made it out too be, imo it could've been explained better with a more "theoretical" approach. Some helpful pointers anyway, especially towards the end of the talk, e.g. take into consideration API versioning from the start.
P.S: wow this platform sucks, you can't edit comments submitted anonymously.
Talk utile a chi non conosceva le .NET web api, ma io che le conoscevo già avrei voluto nella descrizione del talk una bella scritta "come crearle in .NET" così avrei scelto altro.
Sarà stata una mia distrazione ma credevo si parlasse di web api in generale, non di un tutorial su come scrivere Web Api in .NET.
Il talk è stato molto microsoft-oriented e su qualche punto non proprio obiettivo o dettagliato.
Dear all, thanks for your feedbacks, I try to reply to everyone.
1: I tried to reduce to .NET footprint but probably not too much. I needed a platform to explain better some concept. Excuse me for the "slow and sluggish", it was probably due to my medium-level english.
2: I'm sorry the lack of content. I made a mistake while balancing the theory and demos: I had more to say but demos were to long, since I started from scratch. However I think that "not so skilled" and "embarassing" are inapposite.
3-4: You're right, It's what I learned about this session.
5: Come dicevo sopra, ho sbagliato nel bilanciare la sessione secondo me, perchè la necessità di una platform la reputo necessaria. Che poi fosse .NET o qualsiasi altra cosa, ci doveva essere. Se poi parlare di .NET viene interpretato come essere "microsoft-oriented" mi dispiace. Sull'obiettività mi spiace, cerco di esserlo al massimo sempre e mi interessa capire che spunti possano essere sembrati di parte: possiamo approfondire (anche via mail)?
6: Next time (if any) I will try to take away demos to share the "clean" experience without technology. However, "lot of" seems exceeding: it was a single line :) isn't it?
Comments
Comments are closed.
A bit slow and sluggish, too much .NET centered, he had to debug his code during the presentation
Too much lack of content paired with a not so skilled speaker made this talk too boring and embarrassing in some moments. Please get better demos next time and don't focus excessively on a specific technology if the talk is not meant to be
A lot more practical than the description made it out too be, imo it could've been explained better with a more "theoretical" approach. Some helpful pointers anyway, especially towards the end of the talk, e.g. take into consideration API versioning from the start
A lot more practical than the description made it out too be, imo it could've been explained better with a more "theoretical" approach. Some helpful pointers anyway, especially towards the end of the talk, e.g. take into consideration API versioning from the start.
P.S: wow this platform sucks, you can't edit comments submitted anonymously.
Talk utile a chi non conosceva le .NET web api, ma io che le conoscevo già avrei voluto nella descrizione del talk una bella scritta "come crearle in .NET" così avrei scelto altro.
Sarà stata una mia distrazione ma credevo si parlasse di web api in generale, non di un tutorial su come scrivere Web Api in .NET.
Il talk è stato molto microsoft-oriented e su qualche punto non proprio obiettivo o dettagliato.
A lot of buggy live coding, slow. Maybe an interesting introduction to .NET Web Developers nonetheless.
Dear all, thanks for your feedbacks, I try to reply to everyone.
1: I tried to reduce to .NET footprint but probably not too much. I needed a platform to explain better some concept. Excuse me for the "slow and sluggish", it was probably due to my medium-level english.
2: I'm sorry the lack of content. I made a mistake while balancing the theory and demos: I had more to say but demos were to long, since I started from scratch. However I think that "not so skilled" and "embarassing" are inapposite.
3-4: You're right, It's what I learned about this session.
5: Come dicevo sopra, ho sbagliato nel bilanciare la sessione secondo me, perchè la necessità di una platform la reputo necessaria. Che poi fosse .NET o qualsiasi altra cosa, ci doveva essere. Se poi parlare di .NET viene interpretato come essere "microsoft-oriented" mi dispiace. Sull'obiettività mi spiace, cerco di esserlo al massimo sempre e mi interessa capire che spunti possano essere sembrati di parte: possiamo approfondire (anche via mail)?
6: Next time (if any) I will try to take away demos to share the "clean" experience without technology. However, "lot of" seems exceeding: it was a single line :) isn't it?