They’re not programmers, they’re StackExchange plumbers.
-
-
-
this is the best thing I’ve read on twitter dot com
কথা-বার্তা শেষ
নতুন কথা-বার্তা -
-
-
I code with all the features of modern c++, lambdas/templates/stl/etc, but with the express purpose of reducing the amount of code I need to write overall and making sure what's left is readable and requires minimal boilerplate to use
-
meaning I think overcomplicating code is a feature of bad programmers and not modern programmers.
-
I'd argue that modern programming techniques help good programmers write better code, but make it easier for bad programmers to write worse code.
-
I read that as Morse code and I think your point still stands
কথা-বার্তা শেষ
নতুন কথা-বার্তা -
-
-
You are thinking about modern OOP religious approach to programming. Something I call “Baroque C++” with all richness of patterns, facades rules of demeter etc. All the crap that makes your code slower and less readable. :P
ধন্যবাদ। আপনার সময়রেখাকে আরো ভালো করে তুলতে টুইটার এটিকে ব্যবহার করবে। পূর্বাবস্থায়পূর্বাবস্থায়
-
-
-
One of my many pet peeves is when someone drags in a 300k line library because they need a hash function. Or parser.
-
*cough* boost *cough* oh wait that’s like 700Mb!
কথা-বার্তা শেষ
নতুন কথা-বার্তা -
-
-
In what context though? I’m a web development intern and writing as little code as possible seems to be pretty commonplace among us. I’m not trying to start an argument, I’m genuinely curious.
-
In the context of minimizing amount of code solving your particular problem. Version optimized for web development: if you can make a solution in 30 lines of your own code (+ few small tests), for the love of
$deity, do that instead of including another library from NPM. -
Ah! I don’t think anyone has ever told me to write something myself if they knew a solution already existed.
-
This is exactly the pernicious mentality that must be combated! Here's an idea: If you find a solution you love, just copy-paste the code into your project. No extra dependency, no new point of failure! The point is, app devs shouldn't just combine packages like a kid with Lego.
-
Combining Lego bricks is fine. It doesn't work with software libraries, because each brick has a whole set of couple hundreds more attached behind it, most of which you don't need.
কথা-বার্তা শেষ
নতুন কথা-বার্তা -
-
-
And a couple threads. Don't forget the threads.
ধন্যবাদ। আপনার সময়রেখাকে আরো ভালো করে তুলতে টুইটার এটিকে ব্যবহার করবে। পূর্বাবস্থায়পূর্বাবস্থায়
-
-
-
but we have to do information hiding, because later when I'm looking for said information I sure will be happy that I specifically obfuscated it.
ধন্যবাদ। আপনার সময়রেখাকে আরো ভালো করে তুলতে টুইটার এটিকে ব্যবহার করবে। পূর্বাবস্থায়পূর্বাবস্থায়
-
-
-
ধন্যবাদ। আপনার সময়রেখাকে আরো ভালো করে তুলতে টুইটার এটিকে ব্যবহার করবে। পূর্বাবস্থায়পূর্বাবস্থায়
-
-
-
One that I see a lot of the need to "encapsulate" when the entire data set should be on the stack. (Note that "on the stack" could mean like a vector, which is really on the heap, but lives in a stack frame.) You're not going to encapsulate better than a stack frame lol.
-
(aside: you have to be careful what you put on the stack, lest you invoke the overhead of the stack protector)
-
No I just mean, like, the lifespan is function method scope. Designing your logic to be push questions with const inputs into unread output buffers. The actual values can be on the heap... just managed by local variable containers.
-
~Pure functional programming techniques for pretty much any chunk of code that is stateless... and isolating as much as you can into stateless units.
কথা-বার্তা শেষ
নতুন কথা-বার্তা -
লোড হতে বেশ কিছুক্ষণ সময় নিচ্ছে।
টুইটার তার ক্ষমতার বাইরে চলে গেছে বা কোনো সাময়িক সমস্যার সম্মুখীন হয়েছে আবার চেষ্টা করুন বা আরও তথ্যের জন্য টুইটারের স্থিতি দেখুন।