The hottest Substack posts of
William Blankenship
And their main takeaways
- Follow the well-trodden paths when building something and then learn to improve from there.
- Imitating successful models can be a helpful start, but understand that blindly following them may not work for every unique situation.
- Avoid turning from following established paths into aimless wandering; novel problems often arise when charting new territories.
- You need at least two engineers for GraphQL service: for mentoring, supporting, and preventing bottlenecks.
- Invest in tooling like query complexity guards, introspection, and alerts for runtime safety and service performance.
- The skillset needed for GraphQL service is similar to that of a database engineer, focusing on schema design and tool implementation.