|
I'm happy that someone has taken the time to create and maintain such a repository, but I don't think I'll be visiting it anytime soon.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
The Bosque programming language is designed for writing code that is simple, obvious, and easy to reason about for both humans and machines. [NOT IMPLEMENTED YET]
Looks pretty C-ish, but more simple.
|
|
|
|
|
I will be damned for this for sure, but, I have raised the following issue on the GIT site:Quote: Clearly, great progress has been made towards inscrutability, but there are still areas where increased semantic obtuseness can be attained. The use of even a few standard operators ... from the C/C++/C# canon ... like the assignment operator, can be made much more difficult to use.
How about: <= makevar ::string:: => ~some string~
The use of Greek letters from APL could also be considered.
«Where is the Life we have lost in living? Where is the wisdom we have lost in knowledge? Where is the knowledge we have lost in information?» T. S. Elliot
|
|
|
|
|
Well, you could maybe have broken it to him a little more gently, but yes, he does seem to have violated his prime objective.
Whenever you find yourself on the side of the majority, it is time to pause and reflect. - Mark Twain
|
|
|
|
|
At first I read that as "Basque", and I thought Oh heck no.
|
|
|
|
|
I'm not sure what the point of this is. It doesn't appear to be a joke/troll language; but at the same time I'm not seeing anything obviously innovative in 30 seconds of looking at its code.
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, weighing all things in the balance of reason?
Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful?
--Zachris Topelius
Training a telescope on one’s own belly button will only reveal lint. You like that? You go right on staring at it. I prefer looking at galaxies.
-- Sarah Hoyt
|
|
|
|
|
function add2(x: Int, y: Int): Int {
Any language that requires a ":" to separate the variable name and the type, and the type has to be cap-first-letter, requiring me to hit the shift key, is out. And I mean like, kicked out the door with my foot up...
Latest Article - A 4-Stack rPI Cluster with WiFi-Ethernet Bridging
Learning to code with python is like learning to swim with those little arm floaties. It gives you undeserved confidence and will eventually drown you. - DangerBunny
Artificial intelligence is the only remedy for natural stupidity. - CDP1802
|
|
|
|
|
1) Student invents another computer language
2) Company hires student
3) Student insists on publishing his/her toy (code named Giant Waste of Time).
4) Company rolls eyes and tells them to put it GitHub
Step 5 should be: Company tells employee to stop wasting everyone's time and do actual work
6) Computer language is quietly abandoned
|
|
|
|
|
And, how the hell is
function add2(x: Int, y: Int): Int more clear than
int add2(int x, int y) Did April 1 arrive again without me paying attention?
|
|
|
|
|
Well, if they did it like everyone else, there'd hardly be any reason for the language right?
Something that should have stopped them when they started this project.
TTFN - Kent
|
|
|
|
|
If they were really up to the task, the syntax would be more like:
freestanding function called add that takes an int called x and an int called y which returns an int:
return x plus y.
Sincerely,
The Osmonian Order
(sorry if I mispelled He Who Shall Not Be Named - it has been a few years)
|
|
|
|
|
David O'Neil wrote:
freestanding function called addition that takes an number called first number and an number called second number which returns a number called sum:
sum equals first number plus second number.
FTFY
Of at least I think that's closer to the bilge osmo was peddling.
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, weighing all things in the balance of reason?
Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful?
--Zachris Topelius
Training a telescope on one’s own belly button will only reveal lint. You like that? You go right on staring at it. I prefer looking at galaxies.
-- Sarah Hoyt
|
|
|
|
|
'an number'? Ugh! No wonder it was so despised!
|
|
|
|
|
Anyone who built software for a while knows that estimating how long something is going to take is hard. {Stuff} happens
Or put a better way (because there's an xkcd for everything): xkcd: Estimating Time[^]
|
|
|
|
|
My latest: I knew this section would be asynchronous, but not this asynchronous.
Or, after demoing the latest:
"Why isn't it spinning?"
"What are you talking about?"
"This is supposed to spin."
"Since when? It didn't in the reference video."
"Well, it was supposed to."
|
|
|
|
|
Mostly because users want one button to press that does everything for them. To them they think all they asked for was one simple button, how hard can that be, but we have to code that one button to do every task in the right order, and make sure they don't press it at the wrong time or place to save them from themselves.
|
|
|
|
|
OK, you seriously need to study UX before you even touch a keyboard to write code again.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
Implementing all the code for pressing one button is often no big thing but they usually don't tell that it needs to different things depending on a whole bunch of factors.
"They have a consciousness, they have a life, they have a soul! Damn you! Let the rabbits wear glasses! Save our brothers! Can I get an amen?"
|
|
|
|
|
It's an easy enough process, why do people struggle with it?
PHB: How long would it take you to run an export from system X to system Y.
Dev: No idea. System Y is a 3rd party thing, what data does it require from System X?
PHB: Not sure exactly. How long will it take you?
Dev: I don't know what the task is!
PHB: Yes, you do. We want to send data from System X to System Y. How long will it take you?
Dev: Yes, but what data?
PHB: Look, it's a perfectly simple question - how long?
Dev: What data do they want? What format do they want it in? Does System Y have an API?
PHB: No idea, what difference does it make?
Dev: Quite a bit, really ... supposing we just want to throw a smidgeon of data at a well-documented API, then not very long at all but if ...
PHB: "Not very long at all", eh? Brilliant, I'll put it down as a day.
Whenever you find yourself on the side of the majority, it is time to pause and reflect. - Mark Twain
|
|
|
|
|
Quote: However, different tasks may have different uncertainties around 0. We can model this by varying the σ parameter which corresponds to the standard deviation of the normal distribution
So all he did is move the uncertainty of project estimation into the σ parameter, leaving one to still having to estimate σ.
That's helpful.
This should go into the book "How to Lie with Stastics."
Latest Article - A 4-Stack rPI Cluster with WiFi-Ethernet Bridging
Learning to code with python is like learning to swim with those little arm floaties. It gives you undeserved confidence and will eventually drown you. - DangerBunny
Artificial intelligence is the only remedy for natural stupidity. - CDP1802
|
|
|
|
|
I don't need someone else to generate stats that show why software takes longer to develop tahn estimated. I have 'sperience...
0) Lower than required skillset of devs
1) "Urget" requirement changes.
2) Devs that either have to make stuff up as they go, or have to wait for clarification because the requirement docs are crap.
3) Sales people insisting on "insignificant changes" to match new user stories.
4) Managers with no real software dev experience trying to "make their mark" on the project.
5) Someone in management fires all the local devs and outsources to a near-east country because "those guys will work for less", while completely ignoring the time/language barrier, not to mention the general (and PROVEN) lack of quality code they get in return.
6) Sh*t happens.
".45 ACP - because shooting twice is just silly" - JSOP, 2010 ----- You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010 ----- When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
|
|
|
|
|
A novel technique developed by MIT researchers rethinks hardware data compression to free up more memory used by computers and mobile devices, allowing them to run faster and perform more tasks simultaneously. Honey, I shrunk the heap
Compress data, and cache the decompressed. I wonder why no one thought of that before :eyeroll:
I think Chrome does exactly the opposite.
|
|
|
|
|
You've already ripped it to shreds, so I'll just sit back and enjoy it.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
It’s a good indicator that TESS will be able to locate other small planets. Just 53 short light years away. Let's pop over!
|
|
|
|
|
Kent Sharkey wrote: Just 53 short light years away. Let's pop over! photons a minute, but we can tell you what every alien on the planet is eating for lunch! It's so ridiculous that you couldn't make it up.
But they did, anyway.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|