← Înapoi la Urmăritori

Cel mai recent articol

Ultima verificare

Urmăritori 0 urmăritori
Articole: 108
  1. know your frogs 🐸

    The three rules of frogs Eat the frog “The frog” is the task that you need to do the most, but want to do the least.

  2. habit tracker

    There are three stages in a habit; Trigger – something that starts your habit routine.

  3. explain using analogies

    analogies are an effective way of explaining complex topics to non-technical stakeholders.

  4. prefer regular adhoc meetings

    your meeting shouldn’t be recurring, when it can be adhoc.

  5. notion: set full width off 🙏

    Please stop toggling notion to ‘Full Width’.

  6. object storage pricing

    Understanding cloud pricing is pretty tricky.

  7. time complexity

    When solving problems using a computer, we assign “time classes” or time complexities to the problems to describe how long that problem will take to solve.

  8. custom annotation naming

    Custom annotations in Java should be named to describe what’s required of the method, and not which functionality we would like applied.

  9. estimate, predict, forecast

    We are often asked, as engineers, to give estimates for how long a piece of work will take to complete or the complexity of the work.

  10. mfa key recovery

    Some SaaS tools mandate multi-factor authentication (MFA), but this is bad for security and bad UX, until someone solves key recovery.

  11. inclusion

    As a team grows, inclusion becomes harder.

  12. naming is hard

    Software engineers use convergent thinking As software engineers, we engage in a type of thinking called “convergent thinking”.

  13. syncthing

    Syncthing is a peer-to-peer file sync app, this means that each of your devices communicates with it’s peers, within your own private syncthing network structure.

  14. hyperoptic ipv6

    Setup third party router to work with hyperoptic IPv6 Hyperoptic, the UK ISP, offer IPv6 support.

  15. video conferencing

    Many of us have moved to remote working, due to corona virus.

  16. what makes a good software engineer?

    I came across this question, and it got me thinking.

  17. pr checklist

    This post contains checklists that intend to increase the value received from, and ease of, the code review process. checklists reduce complexity Checklists help to capture the information that we often forget.

  18. mvp service level objectives

    Apply “Service level objectives” to product requirements to get an MVP.

  19. beware anecdotal evidence

    Anecdotal evidence comes in many forms, and sounds most believable.

  20. data modelling in saas apps

    Article originally posted on medium.com – When building a SaaS application, there are some similarities between apps, regardless of the service that they provide.

  21. effectiveness as an engineer

    Your effectiveness as an engineer is not defined by the output that you deliver.

  22. brooks law There’s a thing called “Brooks Law” (from mythical-man-month) which explains some of the reasons that software goes slower when adding more humans to a project.

  23. experienced engineers pattern match

    Software engineering is complex not complicated.

  24. short vs. long lifetime structs

    Short vs.

  25. go 1.13: errors.As(...)

    Use return values on errors behaviours when testing with errors.As(...)

  26. the power and danger of consistency

    Humans crave to be, or appear to be, consistent.

  27. High performing teams have a number of characteristics that contribute to their success.

  28. metrics for team contributions

    SMART goals The best goals have metrics associated to them, one method of setting goals is to make them SMART. 1 2 3 4 5 S - Specific M - Measurable A - Achievable R - Realistic T - Timebound The M, and T of smart can be hard to quantify without overly i…

  29. kubernetes generated names

    Naming is hard Naming is hard, especially for kubernetes resources that are some of the lowest possible deployable units, like pods, replication controllers and jobs.

  30. docs requirements

    All organisations need the ability to share knowledge and written communication is one of the most scalable forms.

  31. git: co-authored by

    1 Co-authored-by: <zknill@users.noreply.github.com> You can attribute a commit to more than one author by adding one or more Co-authored-by trailers to the commit’s message.

  32. micromanagement

    The creeping and insidious nature of micromanagement Micromanagement: In business management, micromanagement is a management style whereby a manager closely observes and/or controls the work of his/her subordinates or employees.

  33. go get private repo

    Go Modules Go modules is becomming the standard go dependency tooling.

  34. Keeping a logbook with vim

    There’s a lot to be said for embracing basic tools for getting stuff done.

  35. 2018: reading list

    The computing book’s I’ve read… The Go Progamming Langauge - Alan A.

  36. the cost of extrinsic motivators

    The best output comes from engineers who are intrinsically motivated, according to Dan Pink in his book “Drive”.

  37. options make decisions

    We are makers and solution creators, and as makers optimising for solving problems it’s easy to focus on a working solution.

  38. Limitations of EKS

    On Sep 5, 2018 AWS announced EKS availbility in eu-west-1 (Ireland).

  39. go concurrency correctness

    Go has great concurrency support and as with all concurrent code, it’s very easy to write code that’s doesn’t perform as expected or intended.

  40. proverb driven development

    Learning to drive at 17, my instructor had a bunch of proverbs or phrases that he used to describe different situations that you’d be in as a driver, and what your reaction to them should be.

  41. go's anonymous functions in loops

    In May 2017 I wrote a post about some gotchas in golang from my first few years with the language.

  42. programming mental models

    mental models As complexity grows in projects, decision making, planning, modelling, reasoning, programming!

  43. working with me

    What it’s like to work with me The easiest way to understand someone you work with, or might work with in the future, is to understand a little about them and how they work.

  44. go ast got visitor pattern wrong

    what’s a visitor?

  45. libraries considered harmful

    libraries considered harmful Library is shared code that you cannot otherwise name.

  46. slack @here is bad for your team

    @here Notify active channel members The slack help docs say the @here mention; …lets you notify just the members in a channel who are currently active in Slack.

  47. mastering golang taught me java

    I spend much of my time writing go, but the rest is occupied predominantly by java.

  48. on meetup talks

    I recently gave a talk at London Microservices User Group meetup - video here.

  49. building blocks of go services

    Go has many web frameworks, but none that come with the standard library.

  50. function as an interface

    “An interface type is defined as a set of method signatures.”