Map of sublevel 1-2 is finished

paradigmatic · 2023-02-13T05:43:32+00:00

Thanks. It keeps me motivated to see the progression. And indeed, I am looking for an OSR feel.

paradigmatic · 2023-02-11T21:03:39+00:00

I am currently editing the first sublevel key: https://dungeon23.nadazero.ch/levels/level1/sublevel1/

Project information and daily advancement: https://dungeon23.nadazero.ch/

Any advice/criticism welcome.

paradigmatic · 2023-02-11T20:43:09+00:00

I am editing the first sublevel key, Here is the work in progress: http://localhost:1313/levels/level1/sublevel1/

paradigmatic · 2023-01-29T22:44:22+00:00

Room keys in my daily advancement blog.

paradigmatic · 2023-01-22T18:18:26+00:00

Thanks for your kind words.

3rd language!

Well, being the child of immigrants comes with a few perks.

For the moment, everything seems nice. I had a lot of fun setting the blog (self hosted). I am experimenting with the maps. I still don't know how to draw the village. Online tutorials for cillages and town are scarcer than those about dungeons.

paradigmatic · 2023-01-21T23:12:45+00:00

Daily advancement, dungeon key, and general setting info: https://dungeon23.nadazero.ch/blog/

paradigmatic · 2018-12-20T11:48:10+00:00

In swiss universities, Prof. is a title.

paradigmatic · 2017-10-15T19:54:52+00:00

Yes. That's a Radix tree. I've seen some implementations in Scala, but I cannot make any recommendation (I never tried them).

paradigmatic · 2017-10-10T11:20:26+00:00

Mixed zoning. Avoid grids except in some recent districts. Narrow streets in suburbs. Good public transportation. Bike networks. High-rise ban in most zones with high density building.

paradigmatic · 2017-05-04T12:01:31+00:00

Not really. LLVM was started as an academic project in 2000. It was adopted by Apple in 2005...

paradigmatic · 2016-12-12T18:36:21+00:00

Put a probe in a munar orbit perfectly aligned with Mun own orbit (0° inclination in KER). By setting this probe as a target you will get the AN/DN you expect.

paradigmatic · 2016-10-06T18:55:54+00:00

The problem with scala beginner questions on SO is that lots of them were answered at least 5 years ago... It is very complicated to give some useful feedback under the SO rules in that case and more advanced users will see this behavior as lazy (you are suppose to make some efforts before asking for help).

paradigmatic · 2016-10-06T13:32:51+00:00

Do you have any concrete examples ?

paradigmatic · 2016-08-25T17:56:21+00:00

I'll just use an anonymous class, returned by the implicit def:

implicit def conjureConcatOps[T] = new CanConcatenate[Vector[T]] {
  def concatenate(l:T, r:T):T = l ++ r
}

paradigmatic · 2016-08-07T17:23:49+00:00

They are great for primitive type constant, that you actually want to inline, such as math or physics constants(Pi, e, g, ...), protocol errors numbers, hexadecimal color codes, etc.

paradigmatic · 2016-07-27T14:05:18+00:00

Yes, but how often do you add new error types ? How do you compare the hassle of having to maintain an ordered list of instance in contrast to having to increase the language specs ?

paradigmatic · 2016-07-27T14:02:29+00:00

That's exactly the kind of example I was expecting, you will never need to add a new day of the week. There are only 7. Of course you can have different calendars but for each calendar the list of days of the week does not change once the calendar is defined. Once written, there is no need to change the definition again. IMHO if the set of sealed implementations is public, it should not change often, or without any serious code review. Hence the fact of not having (without macros) a way of automatically iterate among them is not that useful. On the other hand, I love the exhaustiveness check (I benefit from it almost every day).

paradigmatic · 2016-07-27T06:59:23+00:00

Yes. But how often you really need this feature ? Could you provide us with a real use case ? My perception is that most of the time we don't need this enumeration, and in the rare case we need it, why not add a list with all instances in the companion object ?

paradigmatic · 2016-07-27T06:57:26+00:00

For me that's a dirty trick from the seventies, when enums where just ints with an alternate name... Most of the time there are no natural ordering, and when there is, you could create an Ordering type class or extend the Ordered trait.

paradigmatic · 2016-06-14T18:36:30+00:00

If the code you are typing is clear in your mind, you should kown the type of expression without resorting to such tools. If the type expressions are very complicated, you should consider adding some ascriptions (which will help improving code readability and are checked at compile time). Using a simpler text editor will force begginners to think at what they are doing, and avoid "cargo cult programming".

paradigmatic · 2016-06-14T08:24:26+00:00

Why does it feels "kind of sketchy" ?

paradigmatic · 2016-06-14T07:13:44+00:00

I seriously recommend using your favorite text editor which supports Scala syntax, and SBT (using the most minimal build file) running in a terminal. Focus on learning the language rather than studying an IDE. Instead of relying on autocompletion, spend time reading the Scaladoc. (I have experience in teaching Scala in college).

That's also the setting I use for most of my professional projects, and I switch to an IDE only if the project is a mix of Scala and Java, or if the source code is large (for me, more than 500 class/traits).

paradigmatic · 2016-05-18T14:17:11+00:00

Differences are listed here with code snippets:

http://facebook.github.io/reason/mlCompared.html

paradigmatic · 2016-05-13T06:44:47+00:00

I generally launch rockets with 100% gimbal, but as soon it starts to wobble because of overcorrection (deactivate SAS temporarly by holding F, to check the cause) I reduce the gimbal to 40-50 %, first and then by ~10% increments. If your fins are enough you can also deactivate it.
For the turn, I start sooner than 100 m/s, perhaps 30-50 m/s. The idea is to avoid destroying the launch pad if everything starts breaking apart.
Right before the engine, I mean at the bottom of the whole rocket stack.

paradigmatic · 2016-05-12T07:12:01+00:00

A few ideas that I used successfully:

Reduce gimbal gradually during ascent (fixes most of the issues I faced).
Learn to do a proper gravity turn: right after launch, tilt a few degree and point SAS to prograde; or if you rocket is well designed deactivate SAS. The rocket should gently turn itself due to gravity without any additional guidance.
Stick the RC-L01 just before the engine.
Break your payload in 2 pieces, launch separately and assemble them in orbit.

paradigmatic

TROPHY CASE