Software Engineering Quotes retweeted
i'm working on a platform where i link up smart hackers with smart companies. if that interests you, retweet and go join the waitlist: talent.lowlevel.tv/waitlist
Software Engineering Quotes retweeted
Send me better thumbnails for old vids and I’ll give you 100% of the additional income if they perform better than the old ones
Software Engineering Quotes retweeted
I've got an article in my head: "In Defense of Abstractions".
The right abstraction, found at the right time, can save you weeks of work. It's often worth putting the time in.
Software Engineering Quotes retweeted
Earlier today I listened to a friend comment that modern systems have longer keystroke-to-screen latency than an Apple IIe. He meant it as a complaint about bloat and sloppiness.
He's not entirely wrong. But much of that lag is a cost we have paid for flexibility and modularity, and those qualities are worth something.
The software stack under an application running in X on a modern Linux is doing a lot more things than the Apple IIe did; it has to be split into more layers just so the layers will be maintainable. and each joint between those layers introduces latency.
Have we undervalued latency? Are there too many joints? Maybe. On the other hand, human beings are slow creatures. In discussions like this I always bear in mind Jef Raskin's finding that 0.17 seconds is a magic number with respect to the minimum response time of the eye-hand-brain loop.
Human beings can do repetitive actions like drumming on shorter time scales than 0.17s, but not considered and planned actions.
0.17 seconds is a lot of time with respect to any one joint, any one latency hit in the interaction stack. The problem comes when there are many layers and designers aren't aware of how much of that budget the parts of the stack they're not paying attention to are already using.
Of course there's a coordination problem here. In the open-source world, the OS, X, the desktop environment, and the application all typically belong to different dev groups. They're not all reporting to somebody who can notice that aggregate latency is a problem and kick their asses about it. And the problem is worsened by the fact that whole-stack latency is difficult to measure.
However. There is a realistic design rule each layer could adopt that would fix the problem and get the entire keystroke-to-screen time under the Raskin threshold - an equal, measurable constraint on everybody. That is this:
If your layer introduces worst-case keystroke-in-to-keystroke-out latency of more than 0.03 seconds, you're being a bad neighbor to the rest of the application stack and should fix that.
With modern hardware this should be quite achievable. Could be we're already there - but we won't know until we measure.
Software Engineering Quotes retweeted
I'll be on a panel discussion tomorrow (Tuesday June 11th) at 1PM EDT.
Reality Check : AI's True Impact on Software Development.
well.tc/5v9f
Software Engineering Quotes retweeted
We've opened up this position to all of the Americas. So Canada, Mexico, South America. All of it works well enough for the timezone overlap we're looking for with this hire. Pay and setup is the same regardless of where you're from. Apply away!
We have another programmer opening at 37signals. Fully remote, pay between $170,000 - $201,980, eligible for profit share after 2 years, and the chance to work with some amazing people on Basecamp, HEY, ONCE, Rails, Kamal. Oh, and Linux 😄 jobs.rubyonrails.org/jobs/77…
Software Engineering Quotes retweeted
Software design principle: difference should signal meaning. If the parameters to many functions go "x, y, z", then if I have a function with "z, x, y", there better be something special about that function. If there isn't, shuffle the parameters to match the canonical order. #TidyFirst
Software Engineering Quotes retweeted
If you need llms to be able to write time queries heres how, Based on the call with Hamel today for this llm conference
useinstructor.com/blog/2024/…
Software Engineering Quotes retweeted
Recently, I celebrated 10 years professionally in tech(I’ve been in it unprofessionally probably 30 years lol), particularly in software engineering/web development. Here are some lessons I’ve learned along the way:
- As a self taught developer, you CAN NOT skip the basic foundations of Computer Science.
- Always be willing to learn something and step out of your comfort zone.
- Reverse engineer code and break it to learn, just not on production lol.
- Manners and being a likeable person goes a long way.
- Your manager is not responsible for your career growth, but a good manager will pour into and invest in your career growth.
- Integrity and a good reputation is everything.
- When you fail and make mistakes, take accountability and use them as a teaching moment to get better.
- Your title, position, career, etc is not your identity.
- Always help grow someone else.
- FAANG, MAANA or whatever they’re calling it now isn’t the holy grail that people make it out to be. Not getting hired by one of those companies isn’t the end of the world and in this job climate and economy, it’s a blessing in disguise.
- GET OUT of toxic work environments early.
- You don’t have to be the best coder, but be great at problem solving.
- Have a can do approach and attitude, but know when to say no.
- Always over communicate your work, and under promise and over deliver.
- Never let someone’s biases, prejudices and issues define you, your work or your career. YOU ARE GOOD ENOUGH.
- It’s astounding to think about all different verticals, businesses, and government software I’ve contributed to.
Software Engineering Quotes retweeted
Database systems need simple, efficient, and robust hash tables for join processing!
We spill all our secrets in a paper & in the first tech deep dive on our blog:
cedardb.com/blog/simple_effi…
Software Engineering Quotes retweeted
The other day @alexbunardzic shared a Kent Beck quote with me that I've been thinking about constantly ever since:
"If your code is order-dependent, you’ve got a bad design."
So true and yet so little appreciated.
Software Engineering Quotes retweeted
Replying to @hasen_95dx @Hasen_Judi
I disagree about the intent. I personally know the original authors and can vouch for their goal to increase the autonomy of the team and diminish command and control management.
However, you are correct that the outcome, in many cases, has been the opposite. The cause of this reversal was the unintended consequence of certifying “scrum masters”.
RT @martinfowler: FINAL §
Juntao Qiu finishes his article on data fetching patterns for single-page applications. This last pattern is Pre…
Software Engineering Quotes retweeted
The final draft of my programming history book (working title: We, Programmers) is off to the publisher. So my next project is a modernization of Clean Code.
While re-reading the chapter on functions I realized that the silly critiques you can find on-line were written by people who very clearly had not read the book.
Software Engineering Quotes retweeted
Replying to @fima__
The important part of that decision is to identify the trade offs, which you appear to have done.
My preference is to use spies when crossing architectural boundaries like that. If the UCs and Entities are well encapsulated, with all dependencies crossing that boundary towards the entities, then spying should be relatively safe and should help a lot with test execution time and setup complexity.
If, however, the architectural lines are blurred then you may have no choice but to test the UCs and entities together to some extent.















