Page 1 of 41 | Next »
[03:47:49] pipecloud: bricker`LA: https://github.com/postmodern/ruby-install/blob/master/share/ruby-install/ruby/functions.sh#L6-L7
[03:51:19] pipecloud: postmodern: Is there any chance that you could expose the build options that ruby-install would use so I could use them while building unsupported ruby versions for a particular implementation?
[03:52:53] pipecloud: postmodern: I'd just run that from within the directory from the unpacked ruby I downloaded?
[03:53:45] pipecloud: postmodern: I'd just like to compile using the same things ruby-install otherwise uses.
[17:34:20] pipecloud: davidcelis: Is there any offerings from your employer for companies whose security promises to their customers wouldn't allow data leaving their network?
[02:11:33] pipecloud: emocakes: I just use it when I get tired of dealing with divs and arrangement. I guess it sits in grids still.
[02:20:11] pipecloud: epochwolf: Is it just for you or do you want multiple accounts for other users?
[02:21:22] pipecloud: I think most people just want a one-click style mail solution that's open sauce.
[02:36:23] pipecloud: I like how his thoughts on agile are "fuck you, tell me what you want. I don't really want to care about the rest."
[02:37:00] pipecloud: A good way of doing business if you're a consultant, but it sure makes being a full time employee a lot of fun.
[16:22:26] pipecloud: I guess if you like books that lose their value pretty quickly, a rails reference would be the best manifestation of that!
[16:25:35] pipecloud: It changes a lot though. Seems silly to want a physical copy of something so monstrous that changes so much.
[16:30:25] pipecloud: If you're happy with the atrocity, I'm happy enough. Actions at a distance should be made to be easily spotted.
[16:31:12] pipecloud: Plus, I don't believe Rails core has achieved the same level of enlightenment K&R has.
[16:34:21] pipecloud: How am I to be expected to communicate with people when I have to insert my own fucking line breaks around 76 characters? D:
[16:34:41] pipecloud: tubbo: There's rubygems handling notification in a cross-platform way, I'm sure one could script shit up.
[16:40:27] pipecloud: tubbo: I like passing around objects that share a common interface. Often I'm passing around hashes, but if the collection has a collection-y behaviour, I'll wrap that into an object. I'm known more for wrapping a common hash sort into a value object.
[16:41:15] pipecloud: I don't make everything into a value object and then wrap it into a collection object. I generally look for values that travel along together.
[16:41:52] pipecloud: For collections, I look for groups of things I do operations on more than once.
[16:42:19] pipecloud: tubbo: Lastly, if you don't use cathode religiously, I wouldn't pee in your butt if it were on fire.
[17:12:24] pipecloud: Guh, Mail.app is the best terrible graphical application I've used to date. I should find something open source and graphical.
[17:32:47] pipecloud: xybre: I think the important features for me atm is 72-76 width lines and GPG support. I'm hunting things down.
[17:50:29] pipecloud: Hates_: Does that make an SQL query that groups or does it pull them all out into ruby first?
[17:53:53] pipecloud: You could probably slide by with shitty code for a while, but it certainly wouldn't make it past any pull request I review. :)
[17:54:46] pipecloud: xybre: I'm waiting for a good project tracker that's built into the VCS. There are some, but I want a nice one! :D
[17:59:40] pipecloud: xybre: I just wish I knew a nice way to keep stuff in a separate commit tree and work on the project having both in use at the same time. It seems super expensive to constantly query git for parts or whole files. I haven't tried.
[18:02:31] pipecloud: I think my problem is keeping the project checked out while accessing the branch that has the tracker in it.
[18:03:07] pipecloud: Another is syncing. The benefit of a service is no one typically works on the same thing as someone else without someone knowing it.
[18:06:10] pipecloud: xybre: I'd probably just want to configure a 'mirror', an origin, a place where I want to push my changes. Or places.
[18:06:49] pipecloud: xybre: I don't mind not knowing. I mind not being able to work with them to merge.
[18:08:10] pipecloud: xybre: I feel like the warning isn't integral, but it's a nice feature as long as people don't use it as an excuse to do things wrong.
[18:11:29] pipecloud: xybre: I don't want people adding new files or putting things where they don't belong in order to avoid the conflict.
[18:13:32] pipecloud: If they don't get it, they're less likely to do it in order to avoid conflict. The less they know, they more they'll do what they think is right for reasons that aren't "I want to avoid a merge conflict."
[18:14:15] pipecloud: xybre: I don't know if I've ever felt like that's a metric for changing files after I moved from PHP.
[18:15:01] pipecloud: xybre: Unfortunately, my manager doesn't find it as funny as I do to ostracize the bad developers I have to work with from code.
[18:15:50] pipecloud: xybre: I wish I had a manager who'd not only laugh with me but also encourage my antics.
[18:17:27] pipecloud: You'll just have a better understanding of how to fix it ahead of time and your story won't have been worked on in parallel.
[18:18:57] pipecloud: Why not just work and have the first person who finishes help the other person with the conflicts?
[18:23:43] pipecloud: workmad3: I'm usually already busy or pairing, that just wouldn't work for me. I'm not usually editing just one file. They might touch a file, I'm usually working on at least 3.
[18:26:01] pipecloud: workmad3: I just think that my focus and work is more important than possible conflicts that I don't have to care about until after I've committed or when I've decided to merge remote changes in locally.
[18:28:23] pipecloud: We build our project management tools, like planning poker, retros, etc., in google spreadsheets.
[18:31:00] pipecloud: I'm working on a thing called KernelFuckery that basically mixes Array, Hash, and Enumerable's methods into Kernel so you can each(args, receiver &blk)
[18:37:53] pipecloud: xybre: I like something like an object that just handles exposing an interface and just delegates and coordinates.
[18:46:10] pipecloud: workmad3: I don't see the value in pushing that it's grouped. All of them are just objects.
[18:50:19] pipecloud: One is that those objects are just objects, another is that you should organize them.
[18:50:54] pipecloud: xybre: Ohlawdy no. I'm saying that service/behaviour objects are just objects.
[18:51:38] pipecloud: workmad3: "These are just objects. Note that they are also organized by their roles."
[18:52:39] pipecloud: xybre: If you mix the two points of just object and organization, you make it sound like the plain object is a special thing because of its organization. Does that mean other objects aren't other objects or aren't organized?
[18:53:05] pipecloud: "These are organized objects" might be confusing and cause some weird conflation.
[18:55:00] pipecloud: xybre: I'm saying that these objects are just objects. They're also organized by role. To say both at the same time makes it sound like they're just objects that are unique because they're organized.
[18:58:03] pipecloud: xybre: So agreeing that they're just objects, is the distinguishing point between these 'behavioural objects' and others that they're organized in some manner?
[18:58:44] pipecloud: If yes, then you're saying that "Here's objects that are organized" which sounds like others aren't, because surely you wouldn't mention it unless it was some semi-unique trait of the objects.
[18:59:14] pipecloud: xybre: They should also be many things, is it really adding any kind of clarity to mention all the things they should be?
[19:00:04] pipecloud: xybre: I'd probably be old enough to retire by the time I say all that a single object should be.
[19:01:15] pipecloud: xybre: Saying that they should be organized makes it sound like others don't have to. It's like a "no shit, sherlock" thing to say.
[19:04:51] pipecloud: xybre: I think there's more clarity when you say that they're just objects. Saying too much might give the wrong impression. People read into the bullshit I say for some reason.
[19:05:28] pipecloud: xybre: I think that, like all objects, they should be organized cogently, since they are just objects. I personally prefer to keep delivery separated from the rest of the system.
[19:06:20] pipecloud: So often I have multiple services, but in the case of a single place for these objects, I'd probably put them into a gem where they're broken down under a namespace for the kind of interface and behaviour they provide.
[19:08:16] pipecloud: xybre: I've called them service objects a long while, as well as behaviour objects. They're just words that help people understand that the object is encapsulating some state change in the system or coordination.
[19:11:05] pipecloud: That behaviour object, what is it? A service, sure, a coordinator, probably, what's unique about it though? Nothing because it just does what OO is for. Message passing and encapsulation of data and behaviour.
[19:11:46] pipecloud: If I say service object, it's just a hint to think about some verb'ing of some nouns.