JZN666

4 ms·

1.
by JZN666 5y ago
> Code with lots of microdependencies to perform really trivial tasks. "trivial" measure highly relies on programmer's/developer's experience and knowledge. For first developer traversing a tree and applying some
2.
by JZN666 5y ago
> Can you absorb or re-absorb what it is doing rapidly by looking it over for a few seconds? No. Not only because code is essentially poorly structured, but also because I'm not fluent in subject behind a code. Example is operating
3.
by JZN666 5y ago
These properties can be inherited from model/organization itself except "difficult to understand for wrong reasons" and "doesn't work" perhaps. So that's why I point to "respecting to model", a m
4.
by JZN666 5y ago
> non-neccessary complexity with regards to given model (problem, tools)
5.
by JZN666 5y ago
This looks like one of my points: "non-neccessary complexity". Why using "echo" statements if PHP is already designed as procedural web-templating language? If it's not a function that dynamically renders template b
6.
by JZN666 5y ago
* and decomposing a function in smaller functions
7.
Ask HN: What do you consider as “bad” code?
13 points by JZN666 5y ago|36 comments
8.
Ask HN: What is your best type of technical interview?
2 points by JZN666 5y ago|0 comments
9.
by JZN666 5y ago
But this gives very short set of possible function names (up to 20 characters length (?), more is not adequate for development). And even with this parse_str could be named something like "url_parse_query_params_from_str(str)".
10.
by JZN666 5y ago
> I see tons of functions named update_data and get_state and add_items in the business logic sections Maybe they're bounded by some clear context like class or module which serves specific set of tasks? Writing in well designed con
11.
Ask HN: What can lead to misleading names of functions?
3 points by JZN666 5y ago|5 comments