I do what's best at the time. A 45 entry to the downwind is great if you're coming from that direction, but not convenient (or appropriate) when coming from another. Flying over the field then extending out to re-enter on a downwind is a little ridiculous in my opinion, unless it's necessary to blend with traffic.
If I'm coming from the opposite side of the field as the downwind, I may make a midfield crosswind entry, which puts me in a good position to watch the downwind area for traffic and blend in. Sometimes I'll approach straight in at pattern altitude, and perform an overhead "break" or entry from over the numbers; it also puts me in a good position to watch the traffic pattern and look for other aircraft. Sometimes a direct base entry works best. Sometimes a straight in approach works best; in most IFR flying, I arrive via an approach, and unless circling, land straight in off the approach.
Presently, because I leave the traffic pattern low, I often depart contrary to the pattern; if it's left traffic and there's a more direct line with a right turn departing to the fire, I make a right turn. I may never reach traffic pattern altitude; my turn usually begins near the end of the runway (sometimes before), and the crosswind leg is usually initiated well below 100'. It's a long slow climb and turning away from the traffic pattern helps eliminate conflicts, rather than enhancing them. What I don't want is a long climb up into or through the traffic pattern.
Sometimes, conversely, a downwind departure out of a normal traffic pattern works best. Often it's straight-out, with a long, slow climb. It all depends what the needs are at the time. Likewise, I might use a different runway than other traffic is using on arrival; so long as this is timed with and worked in with other traffic, it's not a problem. Yesterday I used a runway that crossed the one most traffic was using. There was enough of a crosswind that I wanted the shorter, more aligned runway for landing, though I was departing downwind on the downhill, longer runway when I was loaded. When landing on the shorter runway, I couldn't see the ends of the long runway, due to trees. I made sure that I closely monitored the pattern, as well as the taxiways and the runway itself, that I'd be landing across, to ensure that nobody was on that runway when my vision became obscured by trees on landing. I certainly didn't want to arrive at the intersection of the two runways when I'd be preoccupied with my landing, to find a conflict.
Couple that watchfulness with appropriate radio calls, and one should do what's best for that particular phase of the operation. I used three different runways for takeoff and landing yesterday, depending on the current winds, and my need to take off or land; takeoffs were on a different runway and a different direction than landings, and I landed two different directions, as well. Each time back to the field was different. Don't get too set on doing things one way. Don't get too set on doing things one way simply because everyone else is doing that, too. Look at your particular flight and even if the aircraft is capable of doing something else, look at your comfort level, your experience, and the nature of your airplane, then decide.
I took off on the longer runway, even though it was downwind with a stronger crosswind, because I weighted twice as much taking off as landing. My performance was limited. Lighter, on return, I didn't want as much crosswind. I could stop a lot shorter than I could takeoff, so a runway aligned into the wind was better for me, and represented a shorter taxi to the reloading pit. Go with what works for you on that particular operation; it may change each time you take off or land, depending on many things. The same may be true of pattern entries or exits. Standardize where convenient, but don't sacrifice operational ability or flexibility, or safety, just to be standard. There is more than one way to skin a cat, and more than one way to enter the pattern or leave it, or take off or land.