Break work down, so it can be done in a day by a developer.
Track daily, i.e. switching to Kanban. If someone gets stuck ask another to help them, don't have too much work in progress at any time.
You're right of course. I assume the OP used a trick by going via IO somehow. Though granted, it might require having a forking server to do the actual summing or using another language, which would be more than 10 lines of code
Frontend and Python developers | London, UK | Picturehouse cinemas
Picturehouse Cinemas Ltd is looking for Python developers and front-end engineers.
Requirements
- Python, html, css, javascript programming experience
- Ability to self-lead, a lot of the time you will be deciding for yourself what to work on.
- Ability to look at big picture architecture as well as small details code.
- Any experience in DevOps is attractive as we handle the full stack.
- 1-2 Days/week in London (Typically at Hackney Picturehouse) every week, rest from home.
About the company
- We have a relaxed, family-friendly culture.
- We contribute to open-source projects
- We have real customers, who care about the product and use it every day
- Free cinema tickets, tickets to premieres,
discounts on food prepared by the chef, free soda
and barista made coffees
- Flexibility in hours and home working (2-3 days/week)
- We use python for almost everything
- Full stack cinema system from POS, ATM to public websites, and internal admin apps.
- A distributed, fault tolerant system so different parts of the business continue to sell in case of failures.
- We sell 25K+ tickets and 30k+ transactions every day across 60+ cinemas.
- We send around 500,000 emails a week and run quite a few websites.
If you are interested, drop me a line - vikram.b at picturehouses.co.uk
Picturehouse Cinemas Ltd is looking for Python developers and front-end engineers.
Requirements
- Python, html, css, javascript programming experience
- Ability to self-lead, a lot of the time you will be deciding for yourself what to work on.
- Ability to look at big picture architecture as well as small details code.
- Any experience in DevOps is attractive as we handle the full stack.
- 2-3 Days in London (Typically at Hackney Picturehouse) every week, rest from home.
About the company
- We have a relaxed, family-friendly culture.
- We contribute to open-source projects, with any non-sensitive code being available for ope
n-sourcing
- We have real customers -- who care about the product and use it every day
- Free cinema tickets, tickets to premieres, discounts on food prepared by the chef, free soda and barista made coffees
- Flexibility in hours and home working (2-3 days/week)
What Python is used for:
- We use python for almost everything
- Full stack cinema system from POS, ATM to public websites, and internal admin apps.
- A distributed, fault tolerant system so different parts of the business continue to sell i
n case of failures.
- We sell 25K+ tickets and 30k+ transactions every day across 60+ cinemas.
- We send around 500,000 emails a week
- We run quite a few websites.
If you are interested, drop me a line - vikram.b at picturehouses.co.uk
We are looking for a Python Developer. We allow plenty of home working, but if you do come into the office, you get free tickets to the cinema we work above (and free barista made coffee).
There's a lengthy description at https://jobs.github.com/positions/9f7647ee-3c66-11e2-961a-fb... but in short we want someone with a lot of Python, who isn't scared by legacy code, and who doesn't require managing. We offer a lot of flexibility and freedom for the right candidates.
Development is run by developers, so we use sexy technologies when they are appropriate. We let people choose what they want to work on, but sometimes we all have to chip in on the grotty stuff.
Do checkout the advert or email us at jobs@newmanonline.org.uk with any questions.
You are the management. It's always your fault. If you didn't actually write the bug. You could have trained the person who wrote the bug. You could have reviewed her code. You could have not let them check it in. You could have not let them work on the feature. You could have not hired them.
You could have fired them.
All this helps you do in a twisted way is figure out who you should fire. Chances are people will leave long before that.
Even though I'm not the boss of my team. Our policy is that it's always my fault. I find it liberating. Gives me an opportunity to learn from all our mistakes. And there is no finger pointing. Unless its at the management. As its always the managements fault.
Get a oven thermometer every oven is different, and you want temp of atleast 220 C, wood ovens have temps of 500 C, so the higher the better. I would even put the grill on.
And put the tray into the oven while it preheats.
For the dough...
Instead of room temp water use cold water (even ice cold water). For the second rise, leave it in the fridge overnight, the idea is to let it rise slowly for a long period of time.
After 2 minutes of pizza being in the oven. Spray with water, I just use the garden water spray. You want mist rather than a pool of water. This will reduce the temp a little, but will give the crust, without having to burn the pizza.
If you are happy with the IDEs then just use them. Having learned both vim and emacs over the past few years. I learned emacs so that I could use slime with lisp. Vim so that I could edit stuff on any server. Emacs has a big learning curve, vim is a bit easier to get into. If you use a mac you can try textmate, I've heard good things about it. On the vim side macvim, gvim are pretty good.
