Live data from Hacker News

IKEA-Oriented Development

taylor.town

81–90 of 146 posts

Re: IKEA-Oriented Development

#81
post #79

Earlier quoted context omitted.

What's the secret to pull those tiny nails?

Use a hammer (or shoe) to gently hit the backplate from the inside, as close to each nail as you can.

Oh, that's right. I remember doing that, a couple of years ago. But looking at my Pax with ~40 nails, it looks like a decent amount of work.

Re: IKEA-Oriented Development

#82
post #29
post #6

Another lesson of Ikea is that often you cannot move them from one home/apartment to another, because if you try to take it apart and then reassemble it, it's never the same. To extend this via analogy to the software realm, a deep refactoring is problematic whereas OTOH a complete rewrite is a better idea. Which has not borne borne out by industry experience.

I have moved many times with Ikea furniture and purchased it used with no problems. Ikea furniture is some of the most disassemble and reassemble-able furniture I've seen.

Everyone seems to chime in with comments confirming your experience, so let me add an opposite take: all IKEA furniture I ever dealt with were... at best, meh. Some may look almost durable when assembled, but they start to accumulate damage over months to years of regular use. Not careless use, but also not super-careful use as if it were a museum piece. Just regular use.

Which is why I too claim that all IKEA furniture I dealt with can barely survive disassembly and reassembly - by the time I wanted them moved somewhere, they've accumulated too much structural damage.

More recently - i.e. in the last 5-8 years - all the new IKEA furniture I dealt with felt... flimsy and dangerous out of the box. Now, a wobbly wardrobe or a bookshelf that looks like it'll break apart if you push it sideways is tolerable in an apartment with two sober, working adults - but the moment a child was to enter the picture, we made sure to screw all IKEA furniture to the wall, and ever since, we don't assemble wardrobes and other "fixed" furniture ourselves - we pay a handyman to do it, and to reinforce them structurally with metal elements and glue, and then screw them to the walls or otherwise do whatever is necessary to ensure nothing will collapse or topple when mishandled by a small child.

In short: to me, IKEA furniture looks nice until you start using it, and is otherwise rather fragile. But it's cheap, and still miles better than any other flat-pack furniture vendor, so like everyone else, that's what we buy.

Re: IKEA-Oriented Development

#83
post #12

Earlier quoted context omitted.

Anecdotally I have had trouble reconciling this seemingly prevalent "you can't disassemble Ikea furniture" with my own experience. It's not made for it sure but bookshelves, bed frames and tables can all be reassembled reasonably well. Anything smaller you can just put in the truck when moving.

Again one of those impossible to kill memes, along with bad mounting instructions (they are on par with Lego, and way better than a lot of industry ones). Usually tells you more about the person making that point than about the point they try to make.

Well, to me, the furniture quality is meh, and they're quite fragile, but instructions are indeed good enough - and miles better than competition.

One thing I specifically appreciate about IKEA instructions is the attention to detail in the drawings. With almost every IKEA purchase, at some point I hit a moment where some elements can be mated in several orientations, and there isn't an obvious way to tell which is the correct one. Sometimes it's apparent if you look couple steps ahead, but I found that you can always find a clue somewhere in the drawing of the unclear step. It's usually something like one of the elements having asymmetrically sized or arranged holes, which translates to a difference of 0.25mm to 1mm between some dots on the paper drawing. It's tiny, but it's always there, corresponding precisely to the piece I have in front of me.

Of course, this could've been done better in many ways, but at least they care about precision of their drawings. Of companies in this space I had experience with, no one else does.

Re: IKEA-Oriented Development

#84

Earlier quoted context omitted.

Why take them apart? Just move them like regular furniture.

Unless you glued them when assembling, moving most IKEA furniture fully assembled puts a lot of stress on the hardware and it permanently loosens up.

but protip: glue your ikea furniture when you assemble it. a little wood glue on the joints makes it 10x sturdier.

Re: IKEA-Oriented Development

#85

Author here! Thanks for sharing :)

Which language is this?

  let points = 0;
  const usrs = await sql`select * from usr where country = 'JP'`;
  for (const usr of usrs) {
    points += usr.points;
  }
I like the approach of not having an ORM to learn.

Re: IKEA-Oriented Development

#86
post #6

Another lesson of Ikea is that often you cannot move them from one home/apartment to another, because if you try to take it apart and then reassemble it, it's never the same. To extend this via analogy to the software realm, a deep refactoring is problematic whereas OTOH a complete rewrite is a better idea. Which has not borne borne out by industry experience.

is there a way we can extend the metaphor here to cover this aspect of ikea furniture?

it's perfectly serviceable and functional, but every time you mention the name people will go out of their way to tell you it isn't, you're wrong, and when you grow up you'll spend 10x as much for the "real" version that does basically the same thing.

Re: IKEA-Oriented Development

#87
post #71

Earlier quoted context omitted.

I've never had a piece of ikea equipment where that applies, I'm typing this on my ikea desk from 2011, next to a 2x2 kallax and another 2x4 kallax that have moved 5 and 3 times respectively.

Well, kallax 2x4 is still a rather light piece of furniture and there's not much need to disassemble it. This need grows with size/weight - e.g. couches, large wardrobes (Pax) etc.

OTOH, I have a 4x4 Kallax that's barely been moved between the rooms couple times in the last few years, and it's already getting wobbly enough that I'm afraid to put much weight on it; it's another of my IKEA furniture pieces that'll end up reinforced with metal angle brackets.

Re: IKEA-Oriented Development

#88
post #6

Another lesson of Ikea is that often you cannot move them from one home/apartment to another, because if you try to take it apart and then reassemble it, it's never the same. To extend this via analogy to the software realm, a deep refactoring is problematic whereas OTOH a complete rewrite is a better idea. Which has not borne borne out by industry experience.

is there a way we can extend the metaphor here to cover this aspect of ikea furniture? it's perfectly serviceable and functional, but every time you mention the name people will go out of their way to tell you it isn't, you're wrong, and when you grow up you'll spend 10x as much for the "real" version that does basically the same thing.

Can we extend the anecdote to make it more accurate and say the opposite: that is, it's fragile but every time you mention it on HN, you'll have 10+ replies saying they personally moved it 13 times between apartments all across NYC, uphill, through snow, both ways, and then still sold it to someone else for a good price?

Re: IKEA-Oriented Development

#89
post #85

Author here! Thanks for sharing :)

Which language is this? let points = 0; const usrs = await sql`select * from usr where country = 'JP'`; for (const usr of usrs) { points += usr.points; } I like the approach of not having an ORM to learn.

It's JS with the wonderful Postgres.js package!

[1] https://github.com/porsager/postgres

Here's an example where it really shines:

  const users = [
    { name: 'Murray', age: 68 },
    { name: 'Walter', age: 80 },
  ];

  await sql`insert into users ${ sql(users) }`;

Re: IKEA-Oriented Development

#90
post #23

Earlier quoted context omitted.

A rewrite is almost never the right choice.

If you have well defined components it is often reasonable to rewrite them. Rewriting an entire project is likely a mistake. I think the mistake is generally the size. If you lock up half of the team and have them rewrite for 2 years then you are likely going to have time. If you slice off components that can be rewritten by a few team members in a couple of weeks you can likely get a good quality result.

No lol, not on anything worth working on. Maybe on something small or with no real users.
Post reply on HN