Content pfp
Content
@
0 reply
0 recast
2 reactions
grin pfp
grin
@grin
what's some programming advice that's considered common sense or that you hear often, but is actually bad advice?
15 replies
7 recasts
16 reactions
grin pfp
grin
@grin
one from me: Postel’s Law is wrong it says “be conservative in what you send, be liberal in what you accept” You should be strict on both If you get a bad message, don’t try to guess. Reply with a clear error and stick to the spec https://en.wikipedia.org/wiki/Robustness_principle
1 reply
0 recast
4 reactions
dusan.framedl.eth pfp
dusan.framedl.eth
@ds8
DRY (don't repeat yourself) - this mostly because it's so easy to detect duplicates even for beginners. it leads to terribly misguided advice and creating stupid abstractions that complicate the code.
4 replies
0 recast
8 reactions
Darryl Yeo 🛠️ pfp
Darryl Yeo 🛠️
@darrylyeo
“If you’re learning frontend, start with React” “Don’t bother learning CSS, just use Tailwind” 🚩🚩🚩
1 reply
0 recast
5 reactions
Cameron Armstrong pfp
Cameron Armstrong
@cameron
Situational, but “it doesn’t need to look pretty, it just has to work” is pretty bad advice for stuff that needs feedback from nontechnical people. Bad/ugly UX and “it’s just a mock-up” things like dummy data is often very confusing and will often derail user interviews in strange ways
3 replies
0 recast
4 reactions
JB Rubinovitz ⌐◨-◨ pfp
JB Rubinovitz ⌐◨-◨
@rubinovitz
“Senior” engineers who just learn and trust in next + vercel and not basic systems design and dev ops concepts.
3 replies
0 recast
4 reactions
Ayush pfp
Ayush
@ayushm.eth
The first question in uni anyone asks when talking about programming is "how many languages do u know" which is bs Doesn't matter after you have picked a few from different levels of the stack
0 reply
0 recast
2 reactions
Darryl Yeo 🛠️ pfp
Darryl Yeo 🛠️
@darrylyeo
object-oriented programming
0 reply
0 recast
2 reactions
Phil Cockfield pfp
Phil Cockfield
@pjc
Similar to @ds8's "DRY" is, or can be, bad (through a sophisticated lens) - I'd say the YAGNI ("you ain't gonna need it") cry. Often you ain't gonna need it - but if you really know the space, you can pre-empt patterns, and tackle them. Also, alot of the time (from a learning perspective) you don't know until you try
1 reply
0 recast
2 reactions
Max Jackson pfp
Max Jackson
@mxjxn.eth
"you should build it in react"
1 reply
0 recast
1 reaction
Darryl Yeo 🛠️ pfp
Darryl Yeo 🛠️
@darrylyeo
“Don’t ask for help; use Google” “Adhering to a style guide is necessary when working in industry” (actual “advice” from professors in my computer science program 🙄)
1 reply
0 recast
1 reaction
Gabriel Ayuso pfp
Gabriel Ayuso
@gabrielayuso.eth
All of it. Learn why the advice is given in the first place and understand when it makes sense and when it doesn't. Sometimes the advice holds, sometimes it doesn't.
0 reply
0 recast
1 reaction
timdaub pfp
timdaub
@timdaub.eth
- TS in combination with ES classes are good and should be used often - dependencies are great, don‘t invent everything yourself - you can‘t make money with open source
0 reply
0 recast
5 reactions
Jackson 🎩🍖 pfp
Jackson 🎩🍖
@jacks0n
Broke: OOP vs FP Woke: procedural is king
1 reply
0 recast
0 reaction
timdaub pfp
timdaub
@timdaub.eth
- comment your code - be consistent
1 reply
0 recast
0 reaction
indy pfp
indy
@indy
"Premature optimisation is the root of all evil" is bad advice, you should be aware of performance issues and architect appropriately. Actual good advice is "premature generalisation is the root of all evil"
3 replies
0 recast
5 reactions