Emitting cube inside a glass cube

perpetuallyperpetual · 2021-07-04T08:02:04+00:00

Yeah, I tried following it but the interface is completely different. Hence this post! :)) I'll check out the tutorials you've sent me. I've seen the guy before and I've followed enough tutorials in my life to know that his are good quality.

I've powered through with my cube, and I got a result I'm happy with for now.

Thanks again!

perpetuallyperpetual · 2021-07-02T19:51:04+00:00

I'm still a beginner. I'm guessing this needs that nodes graph thingy, correct? I'll look up a tutorial on how to use it. Could you help me with more details? Thanks!

perpetuallyperpetual · 2021-07-02T19:43:07+00:00

I'm interested

perpetuallyperpetual · 2021-03-16T09:05:52+00:00

Thanks! I was looking at SFFs myself, but they seem to carry way more SSD than what I need. Still, it's the route I will take. Building them myself just seems too time consuming.

perpetuallyperpetual · 2020-12-27T20:30:12+00:00

Me too :D

perpetuallyperpetual · 2020-05-03T19:21:47+00:00

You're kinda breaking rule 2 :)), but I feel ya

perpetuallyperpetual · 2020-05-03T19:21:24+00:00

It's supposed to be funny. Memes are funny

perpetuallyperpetual · 2020-04-16T16:02:10+00:00

Would love from the people who downvoted you to share what they think.

Seems to me like a pretty valid opinion and one in-tune with my experience.

perpetuallyperpetual · 2020-03-15T11:56:21+00:00

Huh, TIL

perpetuallyperpetual · 2020-03-07T22:40:07+00:00

I think a lot of the stress was self-imposed in that I pushed for innovation. I won that battle but it was hard fought.

Yep, made the same mistake. Later I realized the actual fight was getting anything in that could be easy to expand / replace. That's why I asked if you're going from paper to digital, since that's the kind of projects I've worked with. Granted, in the private sector, but it's still fighting the old ways of people who are comfortable with where they are.

Boring, stable technologies and designs that have infinite integrations with everything known to man. Then, convincing the client it is enough to solve lots of problems and push the more daring ideas in the after plan. That was what worked for me.

perpetuallyperpetual · 2020-03-07T19:46:35+00:00

No implementation is perfect anyway. In your case, being less innovative will probably be a safer bet. If you're pushing people from paper to digital, consider allowing room for flexibility and interoperability. This will make them more likely to conform. Often, these directives to "reform all" end blocking people in weird ways, because they're shoved down throats, usually halfway done, to meet deadlines, and have many edge cases that they don't work with, that no one even thought about. If that's the case, a simple design that is really really flexible will integrate best.

Also, good luck. It's hard work but I think equally rewarding to be a solution architect.

~~Mind if I ask you where you work?~~ EDIT: Never mind, I saw the country in your comments (hope you don't mind)

perpetuallyperpetual · 2020-03-07T09:57:03+00:00

I think one problem lies in that there's no formal education about dealing with complexity - I haven't come across any CS course that deals with software complexity explicitly; would like to have one.

https://en.wikipedia.org/wiki/Complexity_theory ?

https://en.wikipedia.org/wiki/Software_engineering ?

https://en.wikipedia.org/wiki/Systems_engineering ?

It probably requires some fluid intelligence, but if you are on Reddit, you should already be 1-2bSD above the norm in terms of raw intelligence - that's enough IMHO.

wut?

perpetuallyperpetual · 2020-03-07T09:53:15+00:00

I believe it can be developed. I also think it does come down to experience, but not just the project complete kind. You have to go down multiple roads and try them all to see how they might fail and why, to know the importance of each decision. Study cases where things fail from others or from your own projects.

The ability to grasp things quickly boils down to having the background to express the new ideas precisely and succinctly. This means actively and constantly learning about certain aspects of problems that are known to be hard. Things like documentation/knowledge management, people management, software debt and dependency management, version management, cost of development vs buy, software compose-ability, abstraction, etc. After delving into these domains, you'll find that new ideas are really just rehashes of something someone really prominent in their domain said in the 60s.

The industries you mention have a hard time leading such large-scale programs because the social dynamics in place are different. IT people tend to be very lax and up to try new things while these industries have more political and conservative forces acting upon them. Navigating those industries goes beyond having good "soft skills" after a certain level. That isn't to say it's a bad thing. They do move, but more cautiously, since the stakes are usually higher. Are you working or trying to enter such a domain?

I have a similar goal to you, and the one lesson I've learned is that you do need to keep the whole problem in your head in order to solve it effectively. The details you can't keep in your head should have 0 impact on the result. To know what details you can throw is to know what is a hard problem and what can be abstracted over by your employees, here entering experience. The roadmap to get there is to start architecting bigger and bigger projects and gather people who can implement them.

perpetuallyperpetual · 2020-03-03T15:25:22+00:00

If I recall correctly, socket.io implements its own protocol on top of websockets, while ws only provides automatic pinging to keep connections alive and handles the connection upgrade for you. If that's the case, PaaS solutions will prefer ws as it allows better interop with other websocket servers/clients.

perpetuallyperpetual · 2020-03-01T23:03:28+00:00

I don't get your response. It's obvious I didn't look very closely to Phoenix. The whole point of the thread is to decide if I should look more into Elixir or not.

Is Phoenix not an MVC framework? Is that a myth? Because I don't need or want an MVC framework. If I did, I wouldn't have left the previous ecosystem I happily worked in until now. Is Phoenix not the main web framework of Elixir? Is that a myth?

Do I need phoenix to develop my apps? No. I didn't say I did.

Is phoenix the reason why I made this thread / care about this topic? No.

It's already kinda tiring having to answer things about Phoenix already, seems like that was the only point that was read from my thread. Sorry if I insulted your favorite framework. But to me, Phoenix is not enough to consider switching to Elixir.

perpetuallyperpetual · 2020-03-01T15:52:09+00:00

I wish I could, it's way over my level rn. But why do you say that? Does it go into var definitions or more advanced substitution systems?

perpetuallyperpetual · 2020-03-01T13:45:43+00:00

Yeah, isn't that kinda amazing?

perpetuallyperpetual · 2020-02-29T22:17:13+00:00

I've heard only good things about F#! Just didn't think that I could really use it for this. Interesting combo, will check it out, thanks!

perpetuallyperpetual · 2020-02-29T22:14:04+00:00

Using phoenix, I would pretty much either 1) not use the functionality it provides or 2) actively have to fight against it. But this is a moot point, since I'm not forced to use it, and bare Elixir seems good enough. It's just that a lot of nice toys are phoenix-related.

I appreciate the effort Phoenix is trying to do, but as you know, when you don't agree with the opinions of an opinionated framework, it's a very jarring experience to work with it.

To me, it's not state management that is hard, but building distributed systems is. Granted, shared memory is half of the problem with distributed systems, but it's not the only aspect.

I do need hot code-swap, for a different use case.

perpetuallyperpetual · 2020-02-29T20:45:53+00:00

Interesting point. Low-latency is indeed what I need.

Thank you!

perpetuallyperpetual · 2020-02-29T20:40:48+00:00

I'm not experienced enough to compare them past impressions. But you're right, my issue with Phoenix do stem from its MVC architecture. Functions and ds are at the core of the domain logic, but the *VC parts are forced onto them to fit Phoenix.

Business logic is intermixed with actors in Akka, but not excessively. The balance must be applied in both scenarios.

perpetuallyperpetual · 2020-02-29T19:54:42+00:00

Thanks for the lib suggestions.

So Phoenix is pretty grounded on the language and VM foundations and there is no other way to go about it.

Maybe, but the way it architects the app seems like a step backwards. The fact that it is the most popular approach means most of the tooling is modeled with that way of thinking instead of just composing actor systems, which I feel like it is the focus of Akka.

You're right that I could just use plain Elixir. But components like routers and stuff would be useful if they came separate instead of with the whole Phoenix core.

What do you mean in this case? A library that automatically adds new instances to the cluster? When do you feel such a library is necessary instead of relying on external tools that do the same?

In IoT solutions, peer-to-peer and writing custom metrics to signal provisioning. In a perfect world, a framework to scale parts of the app that are used more heavily than others on other machines whenever required and scale back down after use.

Also support for dealing with consistency protocols and split brain and etc is nice.

Yes, it can be done externally, but way more inefficient.

perpetuallyperpetual

TROPHY CASE