I'm hiring a Dev Ops specialist: https://t.co/nNZKI0x4ha
DM me if you're a fit or apply via https://t.co/CmreZvmHvi
It's a rare DevOps role in which you'll wear a hard hat👷to visit our🔋battery sites and inspect the local networking and control hardware!
Not knowing how to code giving you an advantage is absolute nonsense.
The more you understand, the better your prompts, the better the feedback you give, the better product you ship.
What will change is that the intricacies of syntax, compilers, module systems, the finer details of type systems, won’t matter as much to everyone.
But you should absolutely understand how the pieces fit together. From syscall to pixels. Learn how data flows, because you’ll be able to secure your systems. Learn about performance, because you’ll be able to push your agent further. Learn about APIs, because they determine how to integrate systems. Learn about how systems fail, because you’ll be able to make reliable programs.
Getting tired of this <x> is dead trend. The pendulum is swinging too much to the opposite side. Instead of declaring all previous workflows dead, how about we evolve them to suit this new world of AI agents. Prototyping is great and its fantastic that you can do this with much less effort now, but how about you still sit down and *think* about what a good feature entails. It's not one or the other, its both.
After many years of development, I’m excited to share the interior of the first electric Ferrari designed by LoveFrom. Tactile controls and digital interactions blend into one cohesive interface, shaped through deep collaboration across engineering, interaction, graphics, typography, sound, and industrial design. So incredibly proud of the thoughtfulness and care the team brought to every detail.
https://t.co/JZCleflfu7
Whenever a new design to code tool comes around, people get excited. It’s considered the holy grail of design. You can now design with code. This is the final evolution.
But I don’t agree. It’s only the holy grail if you value output higher than the process of design.
Whenever a designer becomes more of a builder, some idealism and creativity dies. Not because building is bad, but because you start out including constraints earlier in the process than they should.
I’m one that very much thinks design is ultimately what is shipped. But before it shipped, there is a lot of stages that don’t benefit from code or some implementation constraints.
In architecture, a lot of the best work is started with sketches and some of the best architects still draw by hand. People forget that the creative process is not about tools. It’s about forming a vision, and then translating that vision into some form. You can use various tools as part of the process, but designers job is really communicating that vision.
Once you become the architect and the builder, or the designer and the developer, you start making more conservative bets. You gravitate to what you already know is feasible or supported. You make smaller iterations. You stop dreaming something big. This is not design.
Designers, don’t do that. Your job is to imagine the future, and sometimes code and convention gets in the way. Use tools. Understand the domain. Get close to the medium.
But don’t lose your greatest strength ability to dream. Work with engineers to realize those dreams.
Designing in code is just a path to local maxima and ruin.
Just a month later and...
🇪🇺 ChatControl is back!
Now they're trying to pass an even more far reaching ChatControl law through the back door, in a form even more intrusive than the originally rejected plan, without needing any of the EU countries votes
The new proposal:
- total mandatory surveillance of ALL text chats, emails and social media in the EU
- obligatory registration of your ID/passport to your chat, email or social media account
- minimum age requirement for chat, email and social media apps of 16 (!)
The only way to stop this law is if EU countries veto it
Read more here by @echo_pbreyer:
https://t.co/Yg2iXX9uWs
@samstooff@riomadeit They're following Apple's Human Interface Guidelines. These guidelines are there for a reason: create design patterns that help users recognize the same behavior within the same platform, not only to make it look nice.
There'll always be more emails in need of reply, more meetings to attend, and more updates to read. A person can fill the entire workweek with these tasks over and over again. But to stay sane and sharp, you must pay yourself first by doing the work that actually means something to you.
I feel this acutely as someone responsible to employees, customers, followers, and readers. I could do nothing all day but check up on projects, people, and posts, but my brain would quickly check out if it was just doing that.
So quite frequently, I just don't. Don't check in, don't check up, and instead dive into the work that checks my own intellectual boxes. Programming for the love of it. Experimenting for the hell of it. Researching for the fun of it.
In another age, I might have been tempted to apologize for such privilege, but screw that. Privilege is wonderful. You should do your best to earn more of it. Even if you have to carve it out of the bare rocks around you.
Ironically, the best way to do that is also to choose to always pay yourself first, however little at first. By solving your own problems, tickling your own interests, chasing your own curiosity. That's where you'll find the motivation to elevate your talent. To turn interest into competency.
And once you've developed some competency, you'll be rewarded with more privilege to build it further. This is the virtuous circle of merit.There'll always be an endless list of work that could be done.
You'll never get through it all and onto your own priorities, if you continue to put them at the bottom.
Zuck on his massive AI researcher deals.
Unlike other Meta software roles, he says building LLMs is like a “group science project” and best to have “the smallest group of people who can fit the whole thing in their head at once.”
So, the investment for each hire can be huge.
why the private network addresses 192.168.*.*?
because a company used it in some early documentation, people literally copied the same while setting up their networks, and that eventually became the standard.
fascinating.