Alessandro Ursino
1.6K posts
Alessandro Ursino
@killanaca
Engineer. Confuse yourself. Loose yourself. Find yourself. Is a cycle of discovery, learning, and revision. 413376540000
London, England 가입일 Temmuz 2009
4.6K 팔로잉350 팔로워
Ma xké dovete fare i titoloni acchiappa click senza avere la minima idea di quello che scrivete?Al momento nn c’è alcun indizio a riguardo, tutt’altro. Questo non è giornalismo. E purtroppo vale per il 90% degli articoli su “cyber” security che appaiono sui quotidiani Italiani.
Ezio Mauro@eziomauro
Cyberattacco su larga scala: giù i siti di New York Times, Guardian, Governo Britannico, Cnn e altri repubblica.it/tecnologia/202… via @repubblica
Italiano
As a #DaftPunk fan but who is no expert on sampling, this video of how #OneMoreTime may have come to life is just fantastic. Kudos to @tracklib #samplebreakdown #RandomAccessMemories twitter.com/i/status/13638…
TRACKLIB@tracklib
Thanks for the memories, Daft Punk 🦾 #daftpunk #samplebreakdown #randomaccessmemories
English
Alessandro Ursino 리트윗함
When making a decision, have a meeting if you're optimizing for speed, write first if optimizing for quality.
Good decisions require clear thinking. Clear thinking requires sitting with the problem to understand it deeply, which writing forces you to confront...
English
Alessandro Ursino 리트윗함
I've just published a blog post about why you should hire a frontend developer for your team. There's so much more to frontend development than HTML, CSS, and JavaScript!
Accessibility, usability, and web performance being the top of the list: technology.blog.gov.uk/2020/07/24/why…
English
Alessandro Ursino 리트윗함
The best and most respected senior/staff/principal engineers I know share this:
1. Humble and approachable. People ask for their advice with zero fear.
2. Lots of experience, but instead of giving answers like “do this”, they’d often coach people to come to a solution themselves.
Emma Bostian@EmmaBostian
Just a friendly reminder that senior and staff software engineers are not “above” or “better than”entry level software engineers. Please don’t let your job title inflate your ego 🙅♀️
English
Alessandro Ursino 리트윗함
@spiunno la copertura mediatica di questa notizia è stata pessima. in pochi hanno realizzato la gravità dell'evento. Gli altri stati non sono esenti da simil errori, anche se spesso suonano come scuse (in tal caso non so quale dei due risvolti è il peggiore) bit.ly/2V47Ko9
Italiano
Alessandro Ursino 리트윗함
20 years ago I built my first website using vanilla HTML & CSS.
If I started web dev today there’s no way I wouldn’t be overwhelmed. Complex frameworks, multiple abstractions, dependencies, git, more frameworks and so many getting started resources.
Frontend in 2020 is tough.
English
Alessandro Ursino 리트윗함
“I guess we can do it faster by skipping tests and not optimising for future use cases.”
vs
“It makes sense to take on tech debt to validate the idea quickly. But we need to repay it if we are to productionize it.”
Same work, but what a difference in expectations setting.
English
Alessandro Ursino 리트윗함
Hello, friends! 👋 At Netflix, we're looking to contract a UX/UI Designer for our Design System team working on the Studio ecosystem. Remote OK!
If you're passionate about design systems, design tools, and libraries, then this is for you! 🎉
My DMs are open, thanks! 🙏
English
Alessandro Ursino 리트윗함
Holy crap! It's finally happening: My book Production Ready #GraphQL is now available for everyone 💫 👇
book.productionreadygraphql.com
English
@__xuorig__ so true, it's got more complicated when a company try to adopt the same "One Graph" for internal tooling with the illusion that they can save time and reuse code. #bastardizedgraphql
English
5/ Not sure where I'm going to with this. But maybe that the "One Graph" utopia a lot of organization seem to be going for has limits, and that there is value in fully autonomous experience based APIs, even with GraphQL.
English
1/ I keep coming back to @pcalcado's post on GraphQL & BFFs: philcalcado.com/2019/07/12/som…
There are so many great points in there. While it's true #GraphQL allows multiple client experiences to co-exist within a same API, that's only one part of the BFF pattern..
English
@NicoloRibaudo the template is still the same after 20 years 😂
English
Alessandro Ursino 리트윗함
One interesting thing about GraphQL is that if you decide you don’t like it, you don’t have to tell me
English
Alessandro Ursino 리트윗함
All JavaScript functions should only be allowed to take one argument. Take an object if you need to pass more than one piece of data.
✅Order independent
✅More Greppable codebase
✅Low cost of adding API
✅predictable pointfree JS
ps. you already do this in @Reactjs as "props"
Ricky@rickyfm
Please quote tweet this with your most controversial javascript opinion, I love controversial javascript opinions
English
Alessandro Ursino 리트윗함
Hey there! I help run one of the busiest websites in the world. Please listen when I say:
Only cache if find you need to. Don't just default to caching everything. It absolutely has downsides in memory, confusion, complexity, races, etc. It's not free. Consider each case.
English