https://sutom.nocle.fr - French wordle referring to old french TV show MOTUS
9 karma · joined February 11, 2013
http://augustin-riedinger.fr/fr/
function my-accept-line() {
# check if the buffer does not contain any words
if [ ${#${(z)BUFFER}} -eq 0 ]; then
# put newline so that the output does not start next
# to the prompt
echo
# check if inside git repository
if git rev-parse --git-dir > /dev/null 2>&1 ; then
# if so, execute `git status'
git status
else
# else run `ls'
ls -l
fi
fi
# in any case run the `accept-line' widget
zle .accept-line
}
# create a widget from `my-accept-line' with the same name
zle -N accept-line my-accept-line
# rebind Enter, usually this is `^M'
bindkey '^M' accept-line
This beautifully works as expected, I never got any bug because of this (as this could be expected for low level aliasing), and it does exactly what I'd expect: get current status of the current folder.
Now typing `git status` elsewhere is such a pain!
function extract () {
if [ -f $1 ] ; then
case $1 in
*.tar.bz2) tar xjf $1 ;;
*.tar.gz) tar xzf $1 ;;
*.bz2) bunzip2 $1 ;;
*.rar) unrar e $1 ;;
*.gz) gunzip $1 ;;
*.tar) tar xf $1 ;;
*.tbz2) tar xjf $1 ;;
*.tgz) tar xzf $1 ;;
*.zip) unzip $1 ;;
*.Z) uncompress $1 ;;
*.7z) 7z x $1 ;;
*) echo "'$1' cannot be extracted via extract()" ;;
esac
else
echo "'$1' is not a valid file"
fi
}
You guys should consider replicating the Wordpress model: open-source tools and paid plans for hosting & support.
Don't think that S3 or github pages are too simple for a user to being autonomous in deployment. IMHO typical use case for your product is a tech guyssetting things up for some non tech people to administrate and write content afterwards.
This means the keys are : - 0 tech steps in administration (no git push, no jekyll generate etc.) - plugins - plugins - plugins - themes - plugins
But clearly if this can become an alternative to WP, this is great because devs hate WP and it scales really bad, while static websites is the complete opposite.
Gmail has an internal behavior that adapts its memory usage on available memory. It may fail in some specific situation (short and wide memory leak), but as a whole the idea is to use RAM as much as possible to make gmail faster.
And yes, gmail lacks of a "low memory consumption" button for those situation where automatic memory usage detection fails.
There is video of google explaining this voluntary behavior but I can't find it unfortunately.
Don't you think the time has come to stop to fake advertising the success of simplicity and to build a proper HN interface? (Just looked at the sources to collapse all subcomments, and I found `<table>` tags, OMG)
I understand the whole "it's simple but it works, people use it"-thing, but what's the point, when [dozen of developpers](https://www.google.fr/search?q=hacker+news+collapse+comments...) are willing to make it for you, even for free.
Not very inspiring for startup builders either.
Fullstack web dev experienced in building startup products. Good UX comprehension and lean methodologies.
I work with Rails, NodeJS and many front-end technologies, my favorite currently being React.
More info and contact on my portfolio: http://www.augustin-riedinger.fr
Some people just don't act rationality, including in their money management. There is nothing to fix here. You could say, "if they are unhappy at the end, there is something to fix".
Most rational people don't understand this because of the logic: you don't want to produce a future unhappiness.
Let's take a softer example: in a winter morning, how should you dress up?
Well, a rational mind would look at the weather forecast, open his window to feel the outside temperature and dress up accordingly.
But some other people won't care. The "effort" required to make the right decision is too high, the gain is too low, why care after all?
For those people, there are three outcomes possible:
1. they took a good decision without the information and will be happier than the rational guys, because they did not have to care about taking the decision and the outcome was good
2. they took a bad decision but still it was not worth the effort and even if they got a little cold during a few hours, they'll make it at the end
3. they took a bad decision which they must turned into bad enough consequences so that they should have cared (eg. they got cold)
And the best is that in category #3, a rational person would learn from what happened and avoid to reproduce it, but being irrational allows the person to not learn from its experience.
The conclusion to this is that since most of our decision making in everyday life is rational, it is hard to understand those who don't act the same way. Also we all are more or less rational, because that's what society forces us to be in respect of the others. But some topic, like how to spend money, or dress in the morning are left to one's freedom, and must not be controlled by some higher rationality.
Nothing proves us that the irrational outcome won't be better that the rational one. What if outcome #1 is the most realistic one?
We are too rational.
Not only are Google interfaces ugly - I agree this is personal - but they remain unusable.
Indeed, they picked up good ideas from others (mobile interfaces from iOS, flat-ish design from Microsoft), but everything is cheap, in a lesser good quality, and particularly not user-friendly.
I'm thinking of:
- the new google maps - the new google drive - the new inbox - their google contact app - google play music - android interfaces as a whole
Please google, keep on being a data-gatherer, data-distributor instead of an app creator, and outsource this to other people who tackle this issue decently.
Remote: yes (preferably)
Willing to relocate: not really
Technologies: Ruby-on-Rails, Front-End/UX (Bootstrap, CSS3, Angular, Backbone), Node.js, anything I could learn interests me!
Résumé/CV: http://aug-riedinger.github.io
Portfolio: http://augustin-riedinger.fr
Email: augustin.riedinger (at) gmail (dot) com
Besides, I'd be curious to read about your app that runs the tests by itself. Are you going to open-source it? Because until now, I only found paying solutions to having a platform running my tests before I deploy, when I'm pretty sure an Heroku app could handle that pretty well...
If you did the coding from scratch to bootstrap your product but don't see yourself as a developer in the long term, then it is all fine: you find yourself other responsibilities in your company (and there will be many to take care of) and let your CTO take care of the developments and hires in the tech team.
On the other hand, if you did this to actually learn to be a good developer reuse that skill later (eg. launch another startup later) then you fall into the questions answered in other replies: is it political or is it only about code quality? (If it is about code quality, maybe your CTO is a jerk saying it this way, but for the sake of your product, it can be logical that you'd be out of its developments...)
As from my own experience, my guess is that you are in between those two situations. In my case, here are the reasons why I was:
- it was good fun bootstrapping the product with little constraints (small team, little production code, few processes, 100% reliability not mandatory etc.): I want to keep doing this
- it can be useful to gain experience into the getting big (team, code base, user base etc.) even if it is less fun
As for now, my best answer to this dilemma is to:
1. know you skills really well to know your value
2. keep innovating as much as possible: when being an entrepreneur (cofounder), your first required talent is not to make sure your code is 100% clean/safe etc. neither is it about having hard processes, but to create new things, to trust your ideas and to make them real. As a matter of fact, YOU cofounded your startup, not your CTO, so remember you have this skill and USE IT!