|
10) Thinking articles paid more per word.
|
|
|
|
|
... the way software is paid per line of code (or brace, or blankline, or comment line, or copyleft line, or ...).
|
|
|
|
|
New Microsoft documentation has revealed a Group policy and Registry tweak that allows you to specify the specific Windows version you wish to stay on and prevent new feature updates from being installed. Should work - at least until the next major update disables it
|
|
|
|
|
|
If it works you should not get the next major update at all
"The only place where Success comes before Work is in the dictionary." Vidal Sassoon, 1928 - 2012
|
|
|
|
|
It’s incredibly likely that your company’s codebase mimics the personality of the engineers contributing to it. To busy rolling my eyes for a proper blurb, sorry.
"The codebase should be a fun place to work"
I know I've been in some "funhouse" codebases, but never... "fun"
|
|
|
|
|
Kent Sharkey wrote: It’s incredibly likely that your company’s codebase mimics the personality of the engineers contributing to it. I thought that was said about dogs and its owners...
M.D.V.
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
Well, most codebases are dogs!
EDIT: And the site that posted the article is aptly named FireHydrant!
modified 29-Jun-20 20:26pm.
|
|
|
|
|
Is this Mediocre Monday? (Re, your links.)
|
|
|
|
|
Gotta give y’all raw meat to chaw on, every once and a while. (But yeah, slowness continues: I keep hoping some brilliance will come out of this pandemic)
TTFN - Kent
|
|
|
|
|
Maybe I should delete those salty comments (wte was I thinking) then?
"Go forth into the source" - Neal Morse
|
|
|
|
|
Apple declined to implement 16 Web APIs in Safari due to privacy concerns | ZDNet
Web Bluetooth - Allows websites to connect to nearby Bluetooth LE devices.
Web MIDI API - Allows websites to enumerate, manipulate and access MIDI devices.
Magnetometer API - Allows websites to access data about the local magnetic field around a user, as detected by the device's primary magnetometer sensor.
Web NFC API - Allows websites to communicate with NFC tags through a device's NFC reader.
Device Memory API - Allows websites to receive the approximate amount of device memory in gigabytes.
Network Information API - Provides information about the connection a device is using to communicate with the network and provides a means for scripts to be notified if the connection type changes
Battery Status API - Allows websites to receive information about the battery status of the hosting device.
Web Bluetooth Scanning - Allows websites to scan for nearby Bluetooth LE devices.
Ambient Light Sensor - Lets websites get the current light level or illuminance of the ambient light around the hosting device via the device's native sensors.
HDCP Policy Check extension for EME - Allows websites to check for HDCP policies, used in media streaming/playback.
Proximity Sensor - Allows websites to retrieve data about the distance between a device and an object, as measured by a proximity sensor.
WebHID - Allows websites to retrieve information about locally connected Human Interface Device (HID) devices.
Serial API - Allows websites to write and read data from serial interfaces, used by devices such as microcontrollers, 3D printers, and othes.
Web USB - Lets websites communicate with devices via USB (Universal Serial Bus).
Geolocation Sensor (background geolocation) - A more modern version of the older Geolocation API that lets websites access geolocation data.
User Idle Detection - Lets website know when a user is idle.
Caveat Emptor.
"Progress doesn't come from early risers – progress is made by lazy men looking for easier ways to do things." Lazarus Long
|
|
|
|
|
It may not be possible for us to ever reach empirical definitions of "good code" or "clean code", which means that any one person's opinion about another person's opinions about "clean code" are necessarily highly subjective. Because 'dirty code' is so much more fun
|
|
|
|
|
There once was a whore from Nantucket,
Who thought clean code was like a bucket
With bits going in, and bits going out,
Oh nevermind, it!
|
|
|
|
|
Clean code goes to production,
Dirty code goes everywhere...
M.D.V.
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
I thought that book was horrible; one of the worse books on coding I've read.
|
|
|
|
|
Let us see.
First came OOP. After 20 years, suddenly you start getting articles on why it is not the panacea it was touted to be.
Then came Agile. Some 20 years later, you start getting talks on why Agile doesn't work in large corporations.
Along came Clean Code and Clean Architecture. Now somebody is saying those emperors don't have any clothes on.
But the snake oil salesmen are not out of tricks yet.
Now you get functional programming. That ought to be good for another 20 years.
And you are all wondering -- nay, enraged -- how programs written in the 60-year-old COBOL still work flawlessly.*
Perhaps the programmers in the old days put a little bit of their heart and soul into their work.
And did not go around disparaging others who worked with different languages on differently architected machines.
But today we have programmers who believe that they are possessors of the Ultimate Truth -- as in Unix, C, etc -- and they are wondering why they are unable to develop good application systems and are grasping for the newest tools, methodologies, frameworks, etc.
Maybe a little humility would be in order.
*I can sit halfway around the world in India and withdraw cash from my account in a small regional US bank from an ATM belonging to a local Indian bank, all because those programs were written in COBOL, tested and put into production on mainframes in the early 1970s by programmers who made do with COBOL, IMS and CICS and not bitterly complain about how they didn't have access to awk, grep or pipes; or that they had to use the Waterfall methodology; or any number of other "blame the tool" excuses.
|
|
|
|
|
A good candidate for post of the month.
|
|
|
|
|
|
I agree with the article.
There are good advices in SOLID, GoF design patterns, automated tests and so on but they should be taken as such, guidelines to keep in mind when implementing solutions.
Trying to be compliant at all the costs with strict rules is wrong. You should use common sense and eventually discuss with other peers what's the best solution.
Each project has its own needs and software is a mix of art, creativity and science. A developer should not obsess if to use this or that design pattern, number of lines per method or number of unit tests.
Do what you think makes really sense and improve code quality, compatibly with the deadlines.
I guess developers obessing with rules are not doing this job for passion but just for the salary.
On the othe hand "gurus" claiming they own the unique source of truth are often smart guys trying to avoid the hard work of writing code and make easy money becoming popular. What kind of super applications they wrote in the past? Probably not many, they are great at theory but nothing special at practice.
|
|
|
|
|
Former Microsoft exec Steve Sinofsky says developers will flock to new Arm-based Mac – but it needs a touchscreen. I can't imagine why he's the ex-Windows boss
|
|
|
|
|
Rings a bell[^]
M.D.V.
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
Like any time you drive past a car dealership and all the mechanic's cars were made by someone else..
In front of the Holden (General Motors) dealership nearby, the mechanics all drive Toyotas, Subarus and Nissans. Not a single one of them drives a Holden..
|
|
|
|
|
I can't see how a $3000 machine should be the future (and that prize includes only a 16" screen)...
It may be true if you speak about large companies (that the cost of the hardware not even mentioned there) - to which he may be used to, but today development rends are more free of those and powered by ideas made on a cheap PC, by singles or small on-line groups...
"The only place where Success comes before Work is in the dictionary." Vidal Sassoon, 1928 - 2012
|
|
|
|
|
ROFL!
Sour grapes, much?
This is the man who thought that touch was the future of everything and refused to listen to hundreds of thousands of Windows users who told him differently.
They were right, he was wrong, and he ceased to be a Microsoft employee because of it.
|
|
|
|