HN user

pbedat

20 karma
Posts0
Comments20
View on HN
No posts found.

The CC vscode plugin can also fetch the errors and warnings reported to vscode by other plugins and language Servers, making the additional compile step obsolete

Turbo is just a JS library, not tied to rails. I use it with golang and I love it! It offers a nice tradeoff between heavy custom HTML attributes and too much 'convention over configuration'. Also pairs nicely with alpine.js

Several framework specific solutions have come to existence to give server-side templating more client side power, in particular:

Ruby/Rails => TurboLinks/Hotwire

Hotwire is not framework specific. E.g. hotwired/turbo is just a JS library that allows for progressive enhancement in basically any web application that renders HTML. I use it in Go and I love it!

I also lost many hours and nerves until I figured it out. But it let me get a glimpse on the true and frightening nature of Microsoft.

Okay so step 1: you try to enable forwarding, but the UI gives you an error about some policy that has to be set

https://docs.microsoft.com/en-us/exchange/recipients-in-exch...

Step 2: you have to find the anti spam settings in a UI called „defender something“ and turn the automatic forwarding polic on.

https://docs.microsoft.com/en-us/microsoft-365/security/offi...

Again the UI doesn‘t allow this because some setting in your organisation is disabled.

Step 3: the hard part. This setting can only be disabled through powershell. Google the name of it and you will find some docs about it.

There might be other ways to achieve forwarding. At least it sounds like that in the docs, but then they must be buried deep below the legacy UIs.

Good luck!

Wait until you have to deal with the admin web apps.

To enable mail forwarding to another domain I had to install powershell and a plugin to install a plugin to allow forwarding in my org.

Then there are times when it says : „To change this setting please enable the legacy UI“

And everything of this convoluted UX hell is documented in a dizzying but highly accurate documentation. I have to give them that!

Switched to protonmail and not looking back.

A very conservative estimation! And it's not only documentation of software but also the requirements and other parts of the whole lifecycle. It's incredible how many companies hold meetings after meetings to keep up the oral tradition only to run in circles. Instead of POs who churn out dozens of irrelevant tickets, we need people who can tell and write stories - real stories not "user stories". They offer insight, motivation, engagement and the right understanding to break down the work into reasonable and deliverable bits.

Curios! I have the same problem. My wife has the theory that I cannot filter all the other distractions well enough. Good to know I'm not alone ;)

There is a really neat JIRA plugin called "structure". That allows you to put issues into a hierarchy. We use these a lot to create roadmap, or breaking down very complex use cases and track the big picture. Would be a first class citizen in my ideal issue tracker.

We recently began migrating a 4 year old and constantly growing angularjs 1.4 app to react. With angular2react and ngreact we don't face a lot of hard decisions, because we may use angular comps in react and vice versa. We have bootstrapped a angular 4/5 app at the same time, but react just feels right.