And its not "Request Demo".... its just submit your email. How do i fall for it every time.
1,475 karma · joined July 22, 2017
And its not "Request Demo".... its just submit your email. How do i fall for it every time.
Go slow and steady, practice daily. Follow justin guitar or pebber brown, sit back and practice over and over again.
And I don't understand it
Isn't that what a patch file gives ?
But then again, I am not saying "don't write the story". If you think you found something worthy, just write a blog post or even a pastebin/gist would be better in terms of the number of people it reaches.
I have never seen any dev searching for error messages in commit messages.
For the rest of the points (makes smarter, builds trust and compassion), if it's so worthy put it on the blog (like this blog post itself) so it can has a potential to reach some reach some audiance.
I bet people will prefer "need to pay" as a shock instead of "locked out" as a shock (with no option of getting your stuff back). I certainly would prefer the former.
I can't believe that this suggested hack is coming from google.
https://bugs.chromium.org/p/chromium/issues/detail?id=914451...
I would alternatively suggest to make the punishment severe and make sure bullies can't get away with it.
So, criminals also, by that logic, themselves need counseling on managing their own needs and emotions rather than punishment ?
> $ complex command here # tagHere
Later use the tag with ctrl+r
I do this all the time
yes, experience is what matters, not success or failure.
https://github.com/mojolicious/mojo/blob/master/lib/Mojo/Dat...
I just find it impossible to glance over it and understand whats happening even though I know what is supposed to be happening there.
Something similar in golang
https://github.com/araddon/dateparse/blob/master/parseany.go
Try reading documentations to see how the 70k+ vocabulary helped the writer and reader.
Sigils like $ and # are even worse. I had to maintain an old perl codebase once (# @_ holds all arguments passed)
This happens when the original code was clever to begin with and someone (else) came try to fix an edge case and lo and behold.
This assumption is false. Either the flows are written in code, are you have to have them in your brain every time you are reading some code which can handle 10 flows.
> solve problems with less code while at the same time keeping that more compact code readable
Less code means less readable.
No. Complexity just makes it harder to read. Go try to read your own code from 5 years ago. I just fail to read even my own code flow every where I used reflections in Java to make it clever (small code which can handle multiple scenarios). Yet I can read every golang codebase in github super easily.
> 2. Google "sets the intellectual trend/fashion"
No. People use what they learn quickly and what gets them productivity. I want to write a software to solve business problems, not want to write software because its cool or something.
Go try to read k8s code. And try to image how it would look like in haskell.
It just looks like you are trying to hate google for the wrong reasons.
I prefer Go over other languages. I like the part that there is no cleverness around it.
But why are you bothered about what google thinks of its engineers ? You can write everything in Haskell, why stop at Java/Rust ?
Said email ended up in spam box as it should have IMO since its from "support@planeeet.com" ?
Show a mailing list subscription page ?
Why not Show when its ready ? and 8 months MVP and not ready ?