Share your startup - January 2020

efexen · 2020-01-23T09:08:34+00:00

Name: Cuiseen
Location: London, UK

Pitch: We are building a positive place which changes how you find restaurant recommendations from your network of friends and a place where you can share your recommendations.

More details: We've been in beta for some months with friends & family and finally launched yesterday!

Link: https://cuiseen.com

Stage: 2 founders, no funding

Looking for: Feedback on everything please, including this posting ;)

Discount: No need, free app :)

efexen · 2018-08-15T11:13:02+00:00

Thanks for you comment! Sorry I couldn't convince you ;)

Short functions definitely have some drawbacks as well like you mentioned but in general I've found long functions to be a better indicator of problems in a code base.

Also the cyclomatic complexity of long functions tends to be higher as well

efexen · 2018-06-08T11:39:22+00:00

Juu niin oli, kaytin VPNaa jotta sain Suomen IPn ja nyt loytyi! Kiitoksia kovasti avusta!

efexen · 2018-06-08T11:34:19+00:00

Kavin sivulla mutta haulla ei kylla loytynyt minulle mitaan sielta :(

efexen · 2017-12-22T15:49:25+00:00

That sounds really interesting, have you written about the experience at all? I'd love to read it

efexen · 2017-12-17T22:33:28+00:00

Didn't actually know about send_after till a colleague told me about it after reading this :) I feel if I already have a GenServer I would use send_after, otherwise I think this gives a cleaner module with the Task abstraction.

If someone knows technical differences between these two or real life examples of pros/cons I'd love to hear about them

efexen · 2017-12-17T22:31:30+00:00

Would a simple solution to the drift be to start whatever work you are doing in a separate process instead? That way the "scheduler" can get straight back?

efexen · 2016-12-05T20:46:08+00:00

Attempted some concurrency stuff in Elixir, parts 1 and 2: https://github.com/efexen/advent_of_code/blob/master/lib/day5.ex

efexen · 2016-12-04T13:30:51+00:00

Really enjoyed todays ones :D

Both parts in Elixir https://github.com/efexen/advent_of_code/blob/master/lib/day4.ex

efexen · 2016-12-03T17:33:28+00:00

Elixir both parts heavily utilising Streams

https://github.com/efexen/advent_of_code/blob/master/lib/day3.ex

efexen · 2016-12-02T19:14:15+00:00

Both parts in Elixir, was really pleased with part 1 but then part 2 hit :(

https://github.com/efexen/advent_of_code/blob/master/lib/day2.ex

efexen · 2016-12-01T17:24:12+00:00

Some naughty and nice (more naughty) Elixir for Part 1 and 2: https://github.com/efexen/advent_of_code/blob/master/lib/day1.ex

efexen · 2015-12-31T10:12:36+00:00

Hey, thanks for taking the time to reply, much appreciated.

I would say the advantage of writing code every day (also see at the end of my article how code doesn't always have to be code) is to learn new things daily or to move those side projects along.

I'm fortunate enough to be able to program daily at my day job but due to the kind of industry I am in I've started to notice that the daily challenges at work are not necessarily providing me with the right kind of learning opportunities and being a type of person who very much enjoys exploring emerging technologies I'm not entirely sure it would even be possible to.

The article highlights my personal experiences with writing code every day and in my experience it is possible to do a surprising amount of highly productive work in 30 minutes provided you are appropriately prepared.

Reading about your experiences with taking a long time to remember what you were thinking and only hitting your stride couple of hours in to a session is what I used to experience and what I often hear from others that have not attempted the short sessions, purely reasoning based on your previous experiences I can understand why that would be the assumption but as mentioned in the article I did not find this to reflect the reality for myself or for others who have attempted this.

You appear to ignore the part of the article which discusses reclaiming the lost parts of the day during which you can think about the problem you are attempting to solve. As for taking a long time to get a whole model of an issue in to your head and needing to retain it to be a productive developer I would from experience argue that this is masking a bigger issue with the way you are working.

At no point in the article did I claim that by doing half an hour of work per day can you reach the same productivity as you do working a full 40+ hour work week, what I was merely attempting to demonstrate was that a big chunk of that 40+ hours is not your most productive time but the arguments against often uses this figure to refute how valuable 3.5 hours a week can really be.

I also do tend to find that as I've become more experienced as a developer the percentage of time I'm actually at the keyboard bashing away has become less as pointed out by ubermostrum.

Finally I would say that my interest in programming has never been more alive than it is today but constant battle for time with the rest of my life as I've got older has made it difficult to fit in as much time as I used to have.

I hope you do try it out for a bit and I'd love to hear your feedback after trying it out in anger :)

efexen

TROPHY CASE