Gareth Repton

Software dev - CSharp, OO, FSharp, Functional, SQL, NoSQL and a bunch of other stuff... like the theory side as much as the practical.

[Gareth Repton @GarethRepton]

#fsharp options are much like #csharp nullables but its how theyre handled that makes them different.
https://t.co/phcr0DdUHy #programming #dotNET

[Gareth Repton @GarethRepton]

@kellabyte There is no silver bullet.

[Gareth Repton @GarethRepton]

Apply this to everything

[Scott Hanselman 🌮 @shanselman]

Screw that. Seriously. Let me show you some of my feedback from my talks.

“Not as funny as he thinks he is.”
“Not technical enough.”
“Too technical”
“What’s with the lip smacking.”
“Just stop.”

David. Keep speaking. F the haters. All y’all. Do the same.

[Prof. Feynman @ProfFeynman]

The statements of science are not of what is true and what is not true, but statements of what is known with different degrees of certainty.

[Gareth Repton @GarethRepton]

@stephenrkell Fortunately when I was at uni we predominantly used the early versions of C#, its still not quite as fun as some languages, but its so much more fun than Java. I agree, theres something about java which just makes things duller somehow.

[Gareth Repton @GarethRepton]

@rtfeldman @7sharp9_exhumed YAGNI and in a similar vein to code over-reuse, speculative generality. EVERYONE has written something violating those two things, its just human nature to do it.

[Gareth Repton @GarethRepton]

@jordan_n_marr @c4fsharp Yeah, I guess my point is that they're not some big new concept for C# devs, they are pretty much the same thing. Its just F# style encourages a better way of handling them, or at least so far thats what I'm finding.

[Gareth Repton @GarethRepton]

#fsharp options are much like #csharp nullables but its how theyre handled that makes them different.
https://t.co/phcr0DdUHy #programming #dotNET

[Gareth Repton @GarethRepton]

@7sharp9_exhumed The difference seems to be pattern matching, pipes, and the simplicity at creating higher order functions. Which are really just standard language features in f#. I started this article thinking options were a new thing, and ended thinking theyre nearly the same as nullable.

[Ben Halpern @bendhalpern]

{ ❤️ }

[Gareth Repton @GarethRepton]

Got 90% of the way through a blog post on option in F#, and I've changed my mind on my original premise, now I have to rewrite half of it :).

[Paul Hudson @twostraws]

“There are two ways of constructing a software design. One is to make it so simple that there are obviously no deficiencies; the other is to make it so complicated that there are no obvious deficiencies. The first method is far more difficult.” – Tony Hoare

[Gareth Repton @GarethRepton]

@GeePawHill I imagine the guideline of returning IEnumerable<T> in .Net world alleviates this problem for the most part. Maybe with the exception that you can leak things out that are actually IQueryable that do weird things when they execute.

[Gareth Repton @GarethRepton]

What I dont know yet is which of the two is better for structuring an application, but I suspect OO right now, and functions for a lot of implementation detail. #fsharp #csharp #dotnet #software #softwaredevelopment 6/6

[Gareth Repton @GarethRepton]

Its really quite interesting learning functional stuff with #fsharp to see just how many of the great features in #csharp are from the functional world. Seriously! Many of the things that I thought were just timesaving language features are functional concepts. 1/6

[Gareth Repton @GarethRepton]

It seems clear that the future (and present for that matter) is going to be as much of a mix of #functional and #objectoriented paradigms as is possible. 5/6

[Gareth Repton @GarethRepton]

This is so true, the patterns used for something that has to be fast, and only "good enough" often dont translate to things requiring complete accuracy.

[Gareth Repton @GarethRepton]

Dev fallacy: The only value of unit tests is the resulting test suite.

Those tests give you the power to fix your code base with confidence whether written before or after. #DevDiscuss