Amal Hussein

14.4K posts

Amal Hussein banner
Amal Hussein

Amal Hussein

@nomadtechie

Engineering Lead.

NYC ↔️ Berkshires ↔️ Boston Katılım Eylül 2013
1.7K Takip Edilen8.1K Takipçiler
Sabitlenmiş Tweet
Amal Hussein
Amal Hussein@nomadtechie·
We need to start normalizing that software engineering can be a 9-to-5 job. It's ok to not live, eat, and breathe tech 24/7. It's ok to be in tech bc it's a lucrative job that pays the bills. You don't need to be passionate about tech to be in tech.
English
48
218
1.6K
0
Amal Hussein
Amal Hussein@nomadtechie·
@mityasmusin @pbakaus Oh god! So much doom and gloom - am I the only one not existentially worried? I have faith in engineers ability to always be in demand and stay relevant as there will inevitably always be new problems to solve.
English
1
0
3
111
Mitya Smusin
Mitya Smusin@mityasmusin·
@pbakaus Let a guy be optimistic for a second, Paul...
English
2
0
1
156
Paul Bakaus
Paul Bakaus@pbakaus·
This is the correct take, albeit I see no reason why engineers also can’t be replaced in a few years (much harder though than replacing coders).
Mitya Smusin@mityasmusin

SWE-turned-plumber because of AI? In other words, how fucked are we? I've been running a software engineering firm for over 8 years. I have worked with hundreds of engineers. Good and bad. Architects and newbies. And I can confidently say that most people misunderstand what's going to happen. 1. Coders vs Engineers Engineers usually work on problems that: a) depend on a number of inputs b) those inputs are usually very unclear and loosely formulated c) involve collective effort and multidisciplinary teams. More often than not, the eventual solution lies outside of where the challenge was initially perceived to be. Even the extreme techno optimists don't predict that AI will be able to tackle that anytime soon. In other words: the code is not the primary value engineers create. Coding is just the result of a deep understanding of the context. Coders, on the other side, take a Figma design and turn it into an HTML file (slightly exaggerating). Those guys are fucked (not exaggerating at all). 2. People Most outsiders don't appreciate how much creating software means working with people. In many cases, it means you need to understand what people desire when they don't understand it themselves. You need to ask the right questions. You need to understand what parts of information to drop. What not to act on. You need to collaborate with team mates. You need to stay within budgets. You need to understand how to make your work future-proof. 3. Soft skills The intersection of being a good programmer and the ability to efficiently work with humans skills is very rare, but the advent of AI will incentivize more people to grow in that direction. Engineers will capitalize on any new tool, just like they always have. But they will apply it to amplify their own understanding of business challenges. AI is a tool. You can compare it to a great framework. It will definitely accelerate the work of great engineers, and one person will be able to do more than they would otherwise. But the technological revolution is far from over, and like any of them before, it will be driven by engineers. In fact, I think it's just getting started. Bottom line: If you're a good engineer, you have nothing to worry about. You create value and connect the dots that an AI is unlikely to be able to connect in the next decade. If you're a monkey coder, learn plumbing.

English
1
0
4
958
Annie Sullivan (@anniesullie.bsky.sociall)
It was so much fun to chat about Core Web Vitals and Interaction to Next Paint with @nomadtechie, @nicknisi, and @rick_viscomi! If you're interested in Core Web Vitals, definitely give it a listen!
JS Party 🪩@JSPartyFM

🤘 New episode of JS Party! 🩺 Get a pulse on your Core Web Vitals 💫 with @rick_viscomi & @anniesullie 🎤 hosts @nomadtechie & @nicknisi 🗂 #javascript #perf #permatters 🎧 jsparty.fm/315

English
2
4
14
2.8K
Amal Hussein
Amal Hussein@nomadtechie·
The point is that would be a massive breaking change in the ecosystem and entertaining it and giving it’s space isn’t the way forward. Things don’t have to be binary - enabling other pkg managers doesn’t have to come at the cost of removing npm. Stoking useless fires in community is also not productive.
English
0
0
2
136
alex (krondor) miller
alex (krondor) miller@lord_krondor·
@nomadtechie @yagiznizipli its just admitting that the node ecosystem doesn't have sufficient agreement on what makes for sufficient pkg management for all users. this isn't an argument to not *maintain* or *support* npm, just to not make it the default. because its not really a default for many
English
2
0
0
138
Amal Hussein
Amal Hussein@nomadtechie·
@karlgroves Fox sponsored Russian propaganda - very sad, but don’t let these morons rile you up.
English
0
0
0
57
Amal Hussein
Amal Hussein@nomadtechie·
@galstar @t3dotgg That’s pretty hot, tbh! I wish we made more space for control flow via generators. Super underutilized in the world of application development, and more commonly used in libraries.
English
0
0
1
163
Amal Hussein
Amal Hussein@nomadtechie·
Corpack works best for yarn and that makes sense the in wider context. Ultimately, the best best path fwd is to A) do nothing since this wasn’t a need being driven from the community. It’s been proven that not being bundled with node has not been a barrier to usage. B) Start bundling yarn, and pnpm bc unbundling npm or enabling it through Corpack isn’t a viable option.
English
0
0
6
344
Amal Hussein
Amal Hussein@nomadtechie·
And as for whether or not to enable Corpack by default (which is a separate but related issue) there are many valid technical reasons raised here by @darcy as to how this creates serious integrity issues, which is in turn will be a source of confusion and bugs for end users: #issuecomment-1970458083" target="_blank" rel="nofollow noopener">github.com/nodejs/node/pu…
English
1
0
3
369
Amal Hussein
Amal Hussein@nomadtechie·
@kitsonk Makes perfect sense! And yes to this!! Thanks so much for sharing context ❤️🙏🏾
English
0
0
1
51
kitsonk.meh
kitsonk.meh@kitsonk·
@nomadtechie Being ex-Deno, it is mostly "a rising tide lifts all boats". A better Javascript/TypeScript eco-system will benefit everyone. Deno Deploy is the commercial angle, running code at the edge. A bigger better ecosystem you are involved in, the greater the opportunity.
English
2
0
3
182
Amal Hussein
Amal Hussein@nomadtechie·
This code is likely a very good read y’all! I’m sure it’s mountains more streamlined than npm’s legacy codebase. Very eager to dig in! Still not clear on the business model though, is this just a value add for the deno ecosystem, or is there some direct revenue stream?
Luca Casonato 🏳️‍🌈@lcasdev

JSR source code for frontend+backend, all of our cloud configuration, the docs, and everything else is now open source on GitHub: github.com/jsr-io/jsr

English
3
0
11
3.2K
Amal Hussein
Amal Hussein@nomadtechie·
@darcy @lcasdev @syntaxfm Thank you both for the share! And looking forward to the birth of vlt as well! The package management space continues to heat up with big bets - so here for this! 🔥🔥🔥🙏🏾
English
0
0
2
88
Amal Hussein
Amal Hussein@nomadtechie·
@brucel I know, that was the most duh and stupid response. Oh really, really??! lol Jeeez, so glad someone other than an developer called them out on that.
English
0
0
2
79