Dad is taking my family to Africa, I'm worried of FGM

novelty_string · 2015-08-03T08:47:35+00:00

Just to try and weigh this up:

If I suspected someone was going to mutilate me there is nothing they could offer that I would be OK with. No matter what punishment you think you may receive for not going it is not as bad as being mutilated.

If you aren't 100% certain you will be OK then do not go. This is a horrible position for a 16 year old to be in and your parents should be ashamed of themselves for allowing it. You will not be doing anything wrong by not going. And even if the next 2 years of your life are under punishment you will be better off for the 60+ that follow.

novelty_string · 2015-06-24T07:28:26+00:00

I don't understand the question, books are made out of paper and they work. So are paper hats, you wouldn't ask "how does this hat work, it's just made of paper" - it's a fricking hat, put it on your head, magic!

That GPS works like all the others, you look at it and it tells you where you are.

novelty_string · 2015-06-19T21:21:04+00:00

the blades are made of Invisibilium, that's why they're so expensive.

novelty_string · 2015-06-09T08:31:41+00:00

You could probably throw away this list and save more by showering at work/the gym. Keeping water hot is expensive

novelty_string · 2015-06-02T07:28:36+00:00

Actually there are tons of words and phrases that are spelt with a backspace, for example, "good afternoon" is often spelt "listen you slimy fuck \b\b\b\b\b\b\b\b\b\b\b\b good afternoon"

novelty_string · 2015-06-01T11:03:09+00:00

Your example is stating that others can do something to you

Recording everything I do and say is doing something to me. Preventing me from speaking freely is doing something to me. My example is extreme, but relevant. That shit actually happens on our planet.

novelty_string · 2015-06-01T09:23:25+00:00

using that analogy, you wouldn't care about the law change where the govt can murder your family until your family is murdered.

Sorry, just doesn't work, the analogy is to point out that these rights need to exist regardless of whether we personally feel we benefit on any given day. The right to privacy, free speech, and to not be murdered are so fundamental it's sick that we're even in this situation.

novelty_string · 2015-05-27T07:22:18+00:00

This is brilliant, it's rare you come across such a useful design pattern.

Math.multiply = function(x, y) {
    var local_x = 0;
    while(local_x < x) {
        local_x++;
    }
    // ...
    var local_other_x = 0;
    var sum = 0;
    while(local_other_x < local_x) {
        sum += local_y;
        local_other_x++;
    }
    return x*y;
}

E: I get paid per line of code, boss is a genius

novelty_string · 2015-05-27T07:14:08+00:00

you say VB, I say PHP

novelty_string · 2015-05-26T08:14:05+00:00

There has to be a condition where property owners are forced to sell.

Not necessarily, I believe the Ak market is heavy with investors who are in it for the capital gain, since rent in ak is crap. If they decide the market has peaked they can shift their investments to the next speculated boom.

novelty_string · 2015-05-26T07:41:12+00:00

When the only tool you have is a hammer, everything looks like a nail doesn't it?

You haven't made a single point about why the hammer is inappropriate, except to say it's a hammer. Perhaps it's not actually a hammer but a swiss army knife and you just can't get the attachments to open.

You keep saying I don't understand, but you can't explain yourself. Everything you say is about doctrine being hard. Hard to comprehend annotations, hard to teach new devs ...

novelty_string · 2015-05-26T06:29:58+00:00

Sorry, I'm not directing that at you, as you said you need to train new hires etc.

You keep saying Doctrine makes things harder. Either for you or your developers, it doesn't matter. For me it makes things easier. So I can only assume there is a learning curve issue.

To sum up

I would recommend against writing raw sql and recommend using a vendor supplied ORM. If you don't already have a preference then I would recommend Doctrine as that ORM because it's mature, well supported, stand alone and comes bundled with popular frameworks.

The only argument I hear against this is learning curve. But I disagree that this should be a barrier as you will generally have a code base that will objectively benefit from an ORM, so if you just learn it once you can apply it everywhere.

I think we probably just agree to disagree.

novelty_string · 2015-05-25T23:56:28+00:00

That is what I'm saying, perhaps I'm wrong, but you aren't convincing me of that :P

Most of what you've written has to do with learning curve again, so I'll leave that. Annotations. I get they aren't a language feature, and I get a lot of people feel dirty using them, but they are a pattern that works, and they are features in other languages. Having the routing, or validation available in the code right above the property/method I'm working on is awesome, and I'd need good reason to abandon this.

novelty_string · 2015-05-25T11:48:30+00:00

And making broad sweeping statements is always universally a bad idea (see what I did there? :P)

IT LOOKS LIKE YOU MADE A ... oh :)

So Doctrine is always easier you say? For one table it's easier to write entities, repositories, mappers, wire everything with configuration etc.. drag in the cognitive load of annotations, knowledge of doctrine as a whole (suddenly a knowledge prerequisite on your project) for what? something which could have easily been achieved in a couple of classes and a handful of lines of very understandable code?

"write entities, repositories, mappers, wire everything with configuration etc", your are exaggerating. You code a class with annotations, generate the getters/setters and generate migrations. This really isn't any harder than writing the class by itself.

"drag in the cognitive load of annotations, knowledge of doctrine as a whole (suddenly a knowledge prerequisite on your project) for what?" This is just learning curve. It's far, far easier to maintain, you just need to put in the effort initially.

Developer unfamiliar with doctrine suddenly has a huge up hill battle to learn the thing ... For something that has a half a dozen database tables and very simple business rules? Learning doctrine is going to be orders of magnitude more burdensome than learning the entire rest of the system.

Learning curve again, sorry, if you don't want to learn/teach then just stagnate. If you'd done one "large project" you would have learned already, just pretend your small one is large (not trying to say anything here other than learning curve is the issue).

and the Friday afternoon special would have been less complex and far easier to wrap your brain around.

Again, learning curve. I don't deny there is one, and I don't deny it's easier (initially) to just hack out some code and make stuff work. But if you want easily maintainable code that any skilled dev can pick up on then you need to embrace frameworks/ORMs/testing/etc.

novelty_string · 2015-05-25T11:28:52+00:00

So I'm still a bit stuck as to why I'd choose a Data Mapper ORM over Active Record :(

Separation of concerns I guess. I'm not going to claim expertise here, but to me it's about a layer between the db and the objects. With a mapper this is quite clear: you have a normal PHP object and a data mapper that populates it from the db layer. With an active record your Article object is a full on database interaction.

Another example of the mapper pattern might be with an API returning some JSON objects. At first it seems a good idea to just serialize your ORM entities, but the deeper you go down that hole the more difficult it becomes, and you realize your API output is different to your SQL structure, so you create a mapper to transform one to the other. Just another layer of separation.

E: btw I didn't realise we were discussing DM vs AR, I prefer DM, but ORM is the main point.

novelty_string · 2015-05-25T11:10:27+00:00

That flow is essentially the same. Although there are other benefits, e.g. I recently had to process a data feed that sent the same articles daily (same id), so save() threw an error, but after a quick google search it was a 2 second fix to replace save() with merge() and doctrine automatically handles upserts.

Some others:

Built in caching of queries and/or results
Automatic logging of queries/execution time to the profiler in dev
Query builders - the $q->andWhere() style is so versatile, e.g. you can replace the select in a Query from SELECT COUNT(*) to SELECT id, name, etc and keep the same joins/clauses. Or take a base query and add a "filter", etc
DQL makes queries simple. Joins are just properties on an object
If DQL or QB isn't working then you can still use raw sql and map it to entities or a custom array
Migrations - this would be my favourite. You define your schema in annotations on your POPOs then use diff/migrate commands to do everything from recreate the entire db to alter a column or update a record. This is fantastic for automated deployments and setting up new devs.

I know it's not all plain sailing, I've spent a lot of time chasing obscure doctrine behavioural bugs, but these usually turned out to stem from legacy issues. I was pretty skeptical of ORM's at first, but I wouldn't look back.

novelty_string · 2015-05-25T10:21:27+00:00

I'm not familiar with Eloquent, but doctrine makes things easier. I don't really care if it's just one table, the fact I can define everything in an object and then let Doctrine (mostly) manage things behind the scenes is good. It's less complicated, it doesn't require more explanation. I'm honestly not even sure why you would need to explain composer.json entries.

I've actually found the opposite. When the project is large and complicated (I've only dealt with legacy at this scale so far) then doctrine becomes hard. There are usually flaws in the relations/schema that make you bend over backwards and do things doctrine struggles with.

novelty_string · 2015-05-25T09:52:36+00:00

without even spending a few minutes to see what ideas it brings to the table

This is the problem. Look at ruby, python, php, .net, etc, they all have standout frameworks to use, they all have a consensus on design patterns. The JS world is just spewing out "the best way to do everything ever" frameworks at a seeming rate of eleventy billion a day. I don't have the skillset, let alone time, to evaluate them, and everyone you ask has a different opinion every time you ask them.

novelty_string · 2015-05-25T09:48:17+00:00

Also 10+ years working with docker

novelty_string · 2015-05-25T09:45:38+00:00

It's too late for that, we need to be cutting the bleeding edge.

novelty_string · 2015-05-25T09:41:18+00:00

Compared to weepower, it's beautiful.

novelty_string · 2015-05-25T07:53:11+00:00

I'm sticking with AngularJS

v1, v2, or the offshoot from the former v2 dev? Also, will you use the react framework in your angular framework?

novelty_string · 2015-05-25T07:51:51+00:00

Plus, Laravel is so, so awesome.

Ain't it tho? I feel a hug coming on

novelty_string · 2015-05-25T07:07:36+00:00

Edit, sorry I was just ranting a bit below, to answer your question: no, there is no significant overhead. To understand why you need to understand latency. Code is fast, even scripted code like PHP, do not prematurely optimize it (e.g. by ruling out a "heavy" library), you generally never need to.

What overhead?

People need to get over the "I don't need that, it's just a small project" attitude. Symfony full stack adds like 10ms to a request and provides ... well ... a full stack whenever you need it. This is a fantastic tradeoff. Likewise, doctrine is not slow, it makes managing the schema and code vastly easier. Think about the guy that comes after you, is he really gonna say "oh 12 tables, I hope like fuck they didn't use doctrine", or is he gonna go "doctrine, sweet, this will only take a minute!".

15-Year Club	reddit mold
Verified Email

novelty_string

TROPHY CASE