LastThursday

The smart thing to do is to take in the whole person. You should do it actively not passively. That means instead of someone just fitting what you want, that you encourage each other to open up, and you mould yourselves to each other over time. People change over time, and your perception of them changes too.

One thing I'm constantly striving for when I do my work is a certain aesthetic quality. For outsiders, coding for computers seems inscrutable, like trying to understand what surgeons are doing with their knives and blood and unrecognizable body parts. Indeed even though us coders share a common language, our own creations can be difficult to digest even for our peers. And mostly, only the surface of our creations ever get exposed, those guts often stay permanently hidden and un-inspected. You would think that under such circumstances that coding would lend itself to being an anarchic process, in the knowledge that nobody else will ever examine our anarchy. After all, aren't we more prone to mischief when not being watched? And so it can be. Big IT projects are notorious for failing to deliver either on time or at all. If you're unfortunate to have a team of anarchists converge in your organisation, then you're probably doomed. Most coders don't care about aesthetics other than providing lip service to "coding standards". They just want to get the job done and get paid, their mistakes and inadequacies and chaos hidden forever inside a mountain of logic. I think that once a certain level of mastery is reached in any discipline, one can't help but let beauty into their process. It starts to become jarring to be lax and ugly. That's not say that imperfection is not allowed. Mastery can be about using imperfection to convey "realness" and "character" and even to deliberately play with it. But that is still using imperfection as an aesthetic (and beautiful) device. Rookies are imperfect through ignorance, masters imperfect on purpose. There are many ways in which code can be beautiful. Like anything else simplicity is often key. Coding has a strong tendency towards chaos and complexity. As ever more things are thrown into the mix, each new thing interacts with every other thing. Like using paragraphs and chapters in a book, code is nearly always split into distinct units, which are then strung together into a working program. But coders are free to compartmentalise their code any way they see fit, and some ways are simpler than others. Often jet engines are designed with many moving parts, where a simple crank handle would suffice - usually to justify time and money spent. Not everything is simple however. Software can be monolithic and super complex. There's nearly an infinite regress of turtles resting on turtles from what the user sees and interacts with to what the CPU and hardware is actually doing underneath. It's layers and layers of translation from a human-oriented view of the world, to one dominated by electrons imprinted with information. Most coders sit squarely in the middle of all that: they need to be good with both understanding people and what they want, and understanding what computers can actually do. We need to understand it all, and be fluent in all that complexity. There is a tendency towards subtlety within mastery. If conciseness is simplicity and that is beautiful, then programs written by masters can often look simple but belie their complexity. Even masters have to keep themselves in check when writing code. Computer languages nowadays provide complex operations with very simple lines of code, but sometimes it is more aesthetic and easier to understand to write things out the long way. Showing your working can lend a helping hand to those that have to look at your creation - especially if they are less experienced. Comprehension in code is a high aesthetic and often overlooked. We coders can have a hard time putting ourselves in others' shoes (it's a common trait), which means we find it difficult to appreciate that those 1000 lines of code need to be understood by others. Often and more importantly, code needs to be understood again by ourselves five years into the future. Sometimes we have to scrap incomprehensible ugly code and start again from scratch. Code can be made easier to read from the start, and code formatting is important and luckily this is largely automated nowadays. More important is consistency of style. Every coder has their own style and foibles; one can often tell who wrote which patch of code. Some coders are undisciplined and chaotic in this respect, without a consistent style. Some (like me) are nearly OCD about how code is presented, even if no-one will ever read it except the one who wrote it. More important still is being able to understand what a piece of code is actually doing. There are a huge number of algorithms (i.e. recipes) that can and are used in computer programs. For example one such algorithm is to sort a list of words or numbers. A decision often has to be made on whether to use a standard "off the shelf" algorithm or roll your own. Most opt for the latter because it's more flexible and things can be tailored to fit the circumstances - but often the former is the better solution. Coders will write their bespoke algorithms, but not explain themselves at all! Most of the life of a coder is sunk in trying to understand others' bespoke solutions, often without the original coder being available to ask questions of. My work is cryptic and non-sexy to most people, and even to myself sometimes. But I still strive for some level of beauty and aesthetics and the satisfaction that comes from it.

Isn't that just moving the goalposts? The OP is about the self: "there is free will" therefore "I am a self". A implies B. It's more like a property of Consciousness that is always Now. Never retrospectively, but You as Consciousness can realize this free agency in each moment. It's kind of like a feeling. I suspect that's what all this free will stuff reduces to: a feeling. The free will pattern, if you like, is this: you decide before, act now, take ownership afterwards. I suspect you could program an AI to run exactly this pattern and then have a "feeling" about it.

There is no free will and there is free will. Both are true at the same time. You all know that free will isn't completely free right? And even then what is being willed exactly? If it's just decision making, isn't that constrained by what is being decided upon and what can be done? If it's ownership of "things that happen" then isn't that always done restropectively? How do you know you're not deluding yourself? Is succumbing to advertising, free will? It's a mess.

Sameness and difference depends on what you choose to focus on. If you put two people together there will be a lot of similarities (two arms, two legs and so on), and differences (sex, height, hair length and so on). So you can argue it both ways: everyone is unique but also everyone is the same. It's not a paradox though, because the things that are different are not the things that are the same. It's possible to be both the same and different simultaneously. Your statement that "everyone is the same" is only half the story. The only reason to have the "everyone is the same" idea, is to counter our inherent bias that difference is bad. Difference is neutral of course and so is sameness.

Sorry I was teasing. It's a bad habit. Those pesky English idioms.

Of course there is... It could be math and science or acting and singing or reading a lot of literature. Lost in translation I think.

There's nothing like bilingualism to expand the brain. The trick with learning any language is using it regularly and with native speakers. There really is no better way. There's nothing wrong with learning two or more languages simultaneously - either it takes up double the time or your learn half as slowly. If the languages are similar, say Spanish and Portuguese, then there will be a lot of crossover in terms of grammar and lexicon - which obviously helps. There is some cognitive interference if words are similar in two languages, but it's not as bad as you think: native speakers will correct you soon enough. I think actually, your English will improve.

Come hike in the UK, we've despatched all the bears and wolves. Leave your gun behind. I'm pretty sure @Sabth is not in the US.

Some of my most spiritual moments have been listening to music. I listen whilst working, I listen whilst driving. I dance to music in the mornings. I use music as a time machine to remind me of good times. I use it to block out the world when it's too much. Music rocks! Other times I don't listen to music, if I want a different kind of presence. I hike silently, I run silently, I read silently. Just do you and don't worry.

Don't give up! Find an easier route. Here's some inspiration:

I have no experience with rainforest, maybe others here do? So can't advise on best things to wear. But if it's hot and humid, then light, breathable clothing is best. On a flat 4km should take about 40-60 minutes. If it's taking 3-4 hours, then it sounds like it will be up and down hills and through dense wood. You'll get very tired! Be prepared. Take plenty of liquid.

The longer the walk the more important that is. Even an hour in the sun could give you bad sunburn. An hour in the rain and cold will drain your will to live or worse give you hypothermia if not appropriately dressed. If you get a downpour and everything turns to mud, your life will be hell if you don't have appropriate footwear.

Hiking is the best! Although if you're just starting out, keep the route as flat as possible and distances small say less than 8 km. Build up to longer distances over time. Don't go to places with very changeable weather, fog, cold, snow. Always start your hikes in the early morning, the earlier the better, you want good daylight. Stick to well defined paths shown on a map. Also try to keep to places where you won't lose phone reception - you never know if you might need assistance. If you're following a map on your phone, then obviously you'll drain your battery - take precautions, either an extra battery/power pack and switch to airplane mode when not using it. Enjoy! Hiking's fun.

I keep having a recurring philosophical thought that bothers me. It goes something like this: There are an infinity of numbers. What is this infinity? To dumb it down completely, imagine putting down a pair of underwear. Then imagine putting down another pair on top of that, and then another, and then another. Ok you get the picture. This type of infinity is then actually a process. It is the process of stacking a tower of ever higher underwear. If you ignore the need for a never ending supply of underwear and the need for all that time to do it in, you're left with a process that repeats without end. The process is made of a repeating block, i.e. the action. So what bothers me? What bothers me is precisely this bit: "Ok you get the picture". This is because it is essentially materially impossible to carry out the task, you have never seen it done nor will you ever see it done. You know there is a finite supply of underwear and your life is finite. So how is it possible to understand what the phrase "Ok you get the picture" is actually referring to? How is it we can imagine a process without end, let alone communicate that fact, when we have never in fact ever seen a process without end? I don't have a clear answer to the conundrum. If our imaginations are based in material reality, then it shouldn't be possible to talk about anything that carries on indefinitely. And yet we have a word like "indefinitely". Maybe we imagine a process which carries on for a long time and use that as a proxy for infinity? But I don't think that's the case. We all seem to know perfectly well what "do this forever" means and it definitely has a different sense from "do this for a very long time". Could it be perhaps that we have a native conception of infinity within our imaginations? The more I think about it, the more I lean that way. I don't know if we're generally very conscious that we have it, and it mostly comes out when using language. But I don't think we need language to "access" infinity within our imaginations: it's not a product of language. We can easily imagine stacking underwear forever without talking to ourselves about it! So that begs the question. If we have infinity natively built in, then does or can that infinity have structure? Or are we only able to grasp a purely platonic conception of infinity stripped of any texture whatsoever? Questions questions. If that infinity were to have structure, then we essentially would be able to create and hold in our imaginations entire universes, in one shot, so to speak. Of course to explore that infinity would take the finite parts of our imaginations an infinite amount of time. The whole thing really is a Pandora's Box and it bothers me.

Seconded! Requires a bit more concentration than my recommendation, but still good.

This guy gives a good overview of different ideas in philosophy:

I'd prefer the word delusion, as in, you believe a falsehood without deliberately deceiving yourself. The big question is can you ever tell the difference between a delusion (falsehood) and actuality (truthfulness)? Probably not. I think the best we have is that we believe that things are true until proven false. But we can be stubborn and believe false things even with evidence to the contrary. Then that would be self-deception. The problem there is, is can we believe the contrary evidence even if it refutes our delusion? How do we stop replacing one delusion with another? People can even be collectively deluded (say miasma theory). Delusion is a type of ignorance or innocence: we don't know what we don't know. Self-deception nearly always serves some sort of purpose and that's why we hold onto it, we choose to do it.

Finity always has an edge or a limit. But an edge always the defines the boundary between two things. Ergo finity always sits within infinity.

Now you're just toying with me. I'm sticking with suck.

Itensity. FFS. That's it. I knew it wasn't peace and calm.

For you to ask the question? For a more Zen answer: because there's no other choice that this. Or maybe perhaps for pure unadulterated infinite creativity? The LOLZ? Or maybe.... I CREATED YOU. Bwahahaha....

Up until now I've seeked, sook, sucken (what is the past tense?). Suck peace and calm. But that was never it. I feel like I want to absorb EVERYTHING. Maybe that's not it either. Union might be closer. Or maybe non-separation is nearer. Magic! F**k I don't know.

My dreams can be weird. I had a whole slew of non-sequitur dreams just before I woke up today. In one a demon "baby" had been deliberately trapped in muddy water under some sort of wooden planking, and was creating angry havoc by using telekinesis on people in the vicinity. In another my sister was performing some sort of ritual to exorcise something from within her and it wasn't going to be pretty - I was outta there! I remember distinctly thinking if I was "far away" enough not to be affected by it. In another an artist with very long hair, was trying to sell me her artwork which seemed to comprise of maps, which I was well tempted with. But one of her side projects was making "goodbye" art. She also seemed to be part of an entourage of older erotic artists dressed in black. Phew. I like the idea of "goodbye" art. There seems to only be a few situations in which we formally say goodbye, and the rest of the time we just wing it, not really knowing what we're doing. In order of severity I can think of funerals, good luck cards and parties when people leave jobs, and just plain saying "goodbye" or "goodnight" to friends or colleagues at the end of the day. Why even do it? Personally I like to think I've never much been bothered about goodbyes. Either, in the sense of the niceties of saying goodbye, or being able to actually let go. I've always felt that most goodbyes are provisional and in some way a pointless activity. As I've got older so much stuff has passed that having said goodbye to every single one of those things would have been overwhelming - indeed there's still ambiguity over whether some staff has passed or not. When is the right time to say goodbye to people or places that change slowly over time? And yet, there's something deeply meaningful about saying goodbye and formalising it into some sort of ritual. With a funeral it marks a definite and fairly condensed boundary after which things are different. It's very similar to a wedding except that is a "hello" ceremony. A funeral is about the process of letting go of a whole bunch of stuff associated with someone close to you. Funerals and weddings are also about mutual acceptance and agreement around a new state of affairs. So it appears that saying goodbye, is both about planting a marker to indicate change and a mutual agreement to that fact. Fundamentally it's a psychological exercise. Without it we're left with ambiguity and uncertainty, both of which can cause suffering and perhaps an inability to let go of things that have passed. I think that we could make goodbyes into an art form. I find good luck cards you give work colleagues a bit crass even if the sentiment is correct. When I say art form, I don't mean a commercialised lowest common denominator art form. Maybe we could create art for ourselves mostly or those close to us and mark the passing of all that stuff that comes and goes in our lives. Art doesn't have to be drawing, but in any media and in any way that suits us at the time. Maybe even it's just a ritual that's done, perhaps marking the end of a day as the sun goes down. Or writing a short goodbye poem about someone you used to love and never let go of. Perhaps getting friends together and officially marking the fact that I'm no longer young and saying goodbye to youth. There are so many things we have to let go of and we ought to let go of. We should get good and comfortable at saying goodbye, and make it into art.

There's definitely an argument for having an exit option if you know you can live indefinitely. But we have a hard enough time with the morality of euthanasia as it is. I mean if you're 200 years old and fed up with being alive, should you have the option to exit then? What about at 150? Earlier?