• 1 Post
  • 79 Comments
Joined 1 year ago
cake
Cake day: June 30th, 2023

help-circle

  • Space in London is really a trade off. Many are there just to kick start their career which in the UK London offers far more opportunities than, say, Birmingham or Manchester.

    It’s the same as why people put up with small apartments in Manhatten. Or Hong Kong to some extent.

    Many live in smaller places early in their career and then when it’s time for marriage / kids they migrate out to the commuter belt where they get larger, nicer places with a more countryside feel and a longer train ride into the city.

    I think the kind of professionals who would buy the above are comparing it to a smaller (nicer) 2 bed flat closer into the city in a greener area but with no personal outdoor space. That’s the trade off. They might have started a family and so just want a little outdoor space for toddlers until they move out somewhere bigger for schools.

    Or some people like living in smaller urban environments and want to get in early into areas that are “gentrifying”. This has happened over and over in London - move into fairly cramped run down area but with easy commute to work - many other professionals do too - more upmarket shops open locally / cafe culture - streets tidy up, prices explode. Then you sell up and move further out for the country village pad and the train ride to work.

    Also, there are many careers in the UK which you can really only pursue in London (or at least it’s where all the opportunities are). Finance / legal / certain arts etc.




  • In my experience when showcasing at the end of a sprint it pays to leave the visuals very unpolished and focus on functionality. Even if it’s trivial to use a UI library or other standard components. I deliberately make it look basic to help management / uses accept “it’s working but needs polishing”. That polish might then be me spending 10% of time on neatening UI, and 90% of time refactoring / fixing tech debt.




  • I have worked for financial institutions that have variations of the last one. If I saw it I wouldn’t even blink. Semi realistic reasons might be:

    Status attribute - because the project is using the base library of [project whatever] which was the brain child of eNtErPrIsE aRcHiTeCt whose hands on skills are useless and the off-shore dev team who assigned [random newbie] because that’s who was available at the time. They used a status attribute because they didn’t know how to get the status of the http response. No-one with budget control is interested in hearing about technical debt at the moment. Everyone has to use it now else the poorly written test classes fail.

    Message code: because “we need codes that won’t ever change even if the message does”. Bonus points if this is, in fact, never used as intended and changes more frequently than…

    Message: “because we still need to put something human readable in the log”. Bonus points x2 if this is localised to the location of the server rather than the locale of the request. Bonus x3 if this is what subsequent business logic is built on leading to obscure errors when the service is moved from AWS East Virginia to AWS London (requests to London returning “colour” instead of “color” break [pick any service you never thought would get broken by this]).

    I have seen it all etc



  • Double_A Nerdy men playing a board game are intidimating? How do women even get anything in life done of they are this fragile? WTF? Do you also want separate women-only schools, and women-only companies?

    Rbmellor Tf are they in separate groups for? Don’t girls know how sexy they look playing cheers?

    System_glitch And the real reason is because women don’t do well against men. They get dominated except for a very small minority. So I orde for women to have more parity, they have women’s chess A biological man competing with them is, statistically, a huge advantage.

    Two others I recall have been since been removed

    Etc