feat(post): lb4 testimonial @achrinza #14
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
mrmodise
requested changes
Apr 4, 2022
blog/2022/2022-04-06-loopback-4-maintianers-testimonial-rifa.md
Outdated
Show resolved
Hide resolved
blog/2022/2022-04-06-loopback-4-maintianers-testimonial-rifa.md
Outdated
Show resolved
Hide resolved
blog/2022/2022-04-06-loopback-4-maintianers-testimonial-rifa.md
Outdated
Show resolved
Hide resolved
mrmodise
reviewed
Apr 4, 2022
blog/2022/2022-04-06-loopback-4-maintianers-testimonial-rifa.md
Outdated
Show resolved
Hide resolved
Member
Author
|
Thanks for your review, @mrmodise! I've applied the changes. PTAL. |
mrmodise
approved these changes
Apr 4, 2022
dhmlau
approved these changes
Apr 5, 2022
Member
dhmlau
left a comment
dhmlau
left a comment
There was a problem hiding this comment.
@achrinza, thanks for writing up this blog post! LGTM, just a minor comment about the title.
I'm thinking whether we want to have a blog post promoting the new blog location and introducing this blog post series about how our maintainers using LB (as discussed in one of the maintainers' call).
blog/2022/2022-04-06-loopback-4-maintianers-testimonial-rifa.md
Outdated
Show resolved
Hide resolved
| @@ -0,0 +1,46 @@ | |||
| --- | |||
| title: LoopBack 4 Maintainer's Testimonial - Rifa Achrinza | |||
| date: 2022-04-01 | |||
Member
There was a problem hiding this comment.
would be good to modify the date to the publish date when the PR is ready to merge.
dhmlau
reviewed
Apr 5, 2022
blog/2022/2022-04-06-loopback-4-maintianers-testimonial-rifa.md
Outdated
Show resolved
Hide resolved
blog/2022/2022-04-06-loopback-4-maintianers-testimonial-rifa.md
Outdated
Show resolved
Hide resolved
Member
Author
|
@dhmlau I've applied your suggestions; PTAL.
#13 is the announcement PR. |
Member
Signed-off-by: Rifa Achrinza <25147899+achrinza@users.noreply.github.com>
achrinza
force-pushed
the
feat/lb-maintainer-testimonial-rifa-achrinza
branch
from
23343ce to
7988805
Compare
achrinza
commented
Sep 8, 2022
|
|
||
| This transitions well into the next great thing about LoopBack 4 - Its flexibility lends itself to being a great candidate for projects that are not related to web APIs. In `@loopback/core`, abstract concepts such as Lifecycle Observers, Servers, and Services provide the foundational building blocks for virtually any enterprise Node.js project. Hence, when we needed to build a CLI, we were able to re-use many of the non-HTTP LoopBack 4 packages, thereby exploiting many of the same abstractions that we came to love with LoopBack 4. Although we had to implement our own "CLI Server", we were able to build one with confidence as we were already familiar with the "LoopBack Way", and were able to progressively build these internal framework extensions with the same principles of exposing as much of the API to the developer, and providing a graceful approach to "step down" from the abstraction. We've been continuing to enhance this CLI framework internally, and were able to progressively iterate it over time to suit our needs, and we hope to be able to contribute it back to the LoopBack 4 open source project in the future once we're confident in its maturity. | ||
|
|
||
| Finally, the major advantage of LoopBack 4 is that it does not hide its configuration files; As alluded to earlier, a starter LoopBack 4 project would contain swaths of configuration files for the TypeScript compiler, Prettier, ESlint, etc. Although this may look intimidating at first, this approach may actually be beneficial to many developers. Due to LoopBack 4's assumption that the developer may tweak these configuration files themselves, there isn't an "ejected" state like many other frameworks. This means that we are able to still utilise the LoopBack 4 CLI, even as we tweak a configuraiton here and there. As such, we were able to learn the ins and outs of a typical LoopBack 4 project while still having the support of the CLI to accelerate our workflow. |
Member
Author
There was a problem hiding this comment.
Suggested change
| Finally, the major advantage of LoopBack 4 is that it does not hide its configuration files; As alluded to earlier, a starter LoopBack 4 project would contain swaths of configuration files for the TypeScript compiler, Prettier, ESlint, etc. Although this may look intimidating at first, this approach may actually be beneficial to many developers. Due to LoopBack 4's assumption that the developer may tweak these configuration files themselves, there isn't an "ejected" state like many other frameworks. This means that we are able to still utilise the LoopBack 4 CLI, even as we tweak a configuraiton here and there. As such, we were able to learn the ins and outs of a typical LoopBack 4 project while still having the support of the CLI to accelerate our workflow. | |
| Finally, the major advantage of LoopBack 4 is that it does not hide its configuration files; As alluded to earlier, a starter LoopBack 4 project would contain swaths of configuration files for the TypeScript compiler, Prettier, ESlint, etc. Although this may look intimidating at first, this approach may actually be beneficial to many developers. Due to LoopBack 4's assumption that the developer may tweak these configuration files themselves, there isn't an "ejected" state like many other frameworks. This means that we are able to still utilise the LoopBack 4 CLI, even as we tweak a configuration here and there. As such, we were able to learn the ins and outs of a typical LoopBack 4 project while still having the support of the CLI to accelerate our workflow. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Signed-off-by: Rifa Achrinza 25147899+achrinza@users.noreply.github.com