Open Side Menu Go to the Top
Register
** UnhandledExceptionEventHandler :: OFFICIAL LC / CHATTER THREAD ** ** UnhandledExceptionEventHandler :: OFFICIAL LC / CHATTER THREAD **

06-20-2017 , 09:18 PM
I can't imagine a place that both respects devs and refuses to give more than a few days for an offer.

My eng lead does our recruiting and goes out of the way even for interns to give extensions if they ask for it
** UnhandledExceptionEventHandler :: OFFICIAL LC / CHATTER THREAD ** Quote
06-20-2017 , 09:51 PM
Quote:
Originally Posted by just_grindin
Kerowo nailed it. It even directly references coding because I remember her discussing the lack of quality code for people to review over and over again and learn from to move past the mediocrity barrier (paraphrased terribly from the talk).
This is very active learning, and not learning from osmosis. Someone is standing over the person saying "yes" and "no." The equivalent to programming would be, as you code, someone is saying "yes" and "no" each time you write a line or function.

I'm not a fan of passive learning in any form, and this certainly is not an example.
** UnhandledExceptionEventHandler :: OFFICIAL LC / CHATTER THREAD ** Quote
06-21-2017 , 01:43 AM
Quote:
Originally Posted by Noodle Wazlib
@kero

I think I'd mostly be happy working at either place, but the time-limited offer place is probably my second choice.

I know the super limited offer is weird, but they are a smallish company with a very good reputation from current and former workers.

Definitely feel stressed to start working and getting experience, but I've also had an astoundingly high resume response rate since I started applying recently. Maybe I shouldn't be so frantic.
If you are crunched for money, accept the time-limited offer and if your #1 choice comes through, feel free to drop it. I find it silly that people get their panties in a twist when they have to burn one bridge out of 1,000,000 other bridges. Just tell them some personal issues came up and you can no longer take the job.

Quote:
Originally Posted by RogerKwok
I can't imagine a place that both respects devs and refuses to give more than a few days for an offer.

My eng lead does our recruiting and goes out of the way even for interns to give extensions if they ask for it
Noodle's offer is for non-dev position. I think we as devs are lucky to be in high demand such that we can be negotiating. There are not many other careers where you can negotiate your salary as an entry-level employee.

I have a friend who out of college, spent 2 weeks negotiating offers between 3-4 companies. If there's one lesson to be learned, there is a lot of wiggle room when you simply push back.

You just have to understand that it is easier to ask for a 10% increase in comp during the offer stage rather than asking for a 10% raise when you are already employed.
** UnhandledExceptionEventHandler :: OFFICIAL LC / CHATTER THREAD ** Quote
06-21-2017 , 02:34 AM
Wow just going through the docker get started tutorial and it's amazing. This is so much better than the virtual box days
** UnhandledExceptionEventHandler :: OFFICIAL LC / CHATTER THREAD ** Quote
06-21-2017 , 04:03 AM
Has anyone else written WPF? Is my initial impression that it's a giant mess accurate? It's horribly unintuitive, anytime I need to do anything I have to look it up and it's frequently way harder than it feels like it should be.
** UnhandledExceptionEventHandler :: OFFICIAL LC / CHATTER THREAD ** Quote
06-21-2017 , 06:20 AM
Quote:
Originally Posted by ChrisV
Has anyone else written WPF? Is my initial impression that it's a giant mess accurate? It's horribly unintuitive, anytime I need to do anything I have to look it up and it's frequently way harder than it feels like it should be.
I have done a little with it on my own time. Seemed like a dated technology that perhaps some legacy code exists for but really not worth the time to learn anything about. Yes and time consuming to learn. Totally not worth the effort to learn on my own time.
** UnhandledExceptionEventHandler :: OFFICIAL LC / CHATTER THREAD ** Quote
06-21-2017 , 03:37 PM
Quote:
Originally Posted by jmakin
Wow i'm really diggin c#
used LINQ yet?
** UnhandledExceptionEventHandler :: OFFICIAL LC / CHATTER THREAD ** Quote
06-21-2017 , 03:46 PM
Quote:
Originally Posted by ChrisV
Has anyone else written WPF? Is my initial impression that it's a giant mess accurate? It's horribly unintuitive, anytime I need to do anything I have to look it up and it's frequently way harder than it feels like it should be.
ya I had to edit some wpf stuff. its pretty bad imo.
** UnhandledExceptionEventHandler :: OFFICIAL LC / CHATTER THREAD ** Quote
06-21-2017 , 04:37 PM
Quote:
Originally Posted by ChrisV
Has anyone else written WPF? Is my initial impression that it's a giant mess accurate? It's horribly unintuitive, anytime I need to do anything I have to look it up and it's frequently way harder than it feels like it should be.
Executive Summary: run away, run away...

I was under the impression that WPF was dead as far as future development, but it's been a while since I looked. Maybe that's not true. The company I work for rewrote a very large .NET client application from WinForms into WPF, and I don't really feel like it was worth the effort. On the other hand, it also seemed like we went about it in the dumbest possible way. We don't really have UI designers who just write XAML, so there didn't seem to be much benefit to the separation.
** UnhandledExceptionEventHandler :: OFFICIAL LC / CHATTER THREAD ** Quote
06-21-2017 , 05:35 PM
Quote:
Originally Posted by Victor
used LINQ yet?
No not yet
** UnhandledExceptionEventHandler :: OFFICIAL LC / CHATTER THREAD ** Quote
06-21-2017 , 08:09 PM
When styling a react component do you basically just start with it defined in render as styles and move to css when you need media queries? Media queries are still necessary, yes?
** UnhandledExceptionEventHandler :: OFFICIAL LC / CHATTER THREAD ** Quote
06-21-2017 , 08:43 PM
we use https://github.com/gajus/react-css-modules at work

if you're going toy-app, inlining styles is fine but i'd start w/ something more robust
** UnhandledExceptionEventHandler :: OFFICIAL LC / CHATTER THREAD ** Quote
06-21-2017 , 10:51 PM
Quote:
Originally Posted by well named
Executive Summary: run away, run away...

I was under the impression that WPF was dead as far as future development, but it's been a while since I looked. Maybe that's not true. The company I work for rewrote a very large .NET client application from WinForms into WPF, and I don't really feel like it was worth the effort. On the other hand, it also seemed like we went about it in the dumbest possible way. We don't really have UI designers who just write XAML, so there didn't seem to be much benefit to the separation.
What's the new hotness if not WPF then?

I'm not convinced that "UI designers who just write XAML" are a thing. You need to be a programmer to write XAML, because of the insistence on using XML not just for documents, like God intended, but for styling metadata, which is horribly verbose and unintuitive. Here's styling a button in CSS:

Code:
.defaultbutton {
    background-color: white;
}

.defaultbutton:hover {
    background-color: blue;
}
Clear, readable. Here it is in XAML:

Code:
<Style x:Key="DefaultButton" TargetType="{x:Type Button}">
    <Setter Property="Background" Value="White" />
    <Style.Triggers>
        <Trigger Property="IsMouseOver" Value="True">
            <Setter Property="Background" Value="Blue"/>
        </Trigger>
    </Style.Triggers>
</Style>
Just kidding. That actually won't work, because in a typically WPF move, you can't directly style a button because of [insert some ridiculous explanation about Windows system calls here]. This is what is actually required to achieve the desired effect:

Code:
<Style x:Key="DefaultButton" TargetType="{x:Type Button}">
    <Setter Property="Background" Value="White" />
    <Setter Property="Template">
        <Setter.Value>
            <ControlTemplate TargetType="{x:Type Button}">
                <Border Name="wrapper"
                Width="{TemplateBinding Width}"
                Height="{TemplateBinding Height}"
                BorderBrush="{TemplateBinding BorderBrush}"
                BorderThickness="{TemplateBinding BorderThickness}"
                Margin="{TemplateBinding Margin}"
                Background="#01000000">
                    <Border Name="inner" Background="{TemplateBinding Background}">
                        <ContentPresenter Margin="{TemplateBinding Padding}"
                                            HorizontalAlignment="Center"
                                            VerticalAlignment="Center" />
                    </Border>
                </Border>
            </ControlTemplate>
        </Setter.Value>
    </Setter>
    <Style.Triggers>
        <Trigger Property="IsMouseOver" Value="True">
            <Setter Property="Background" Value="Blue"/>
        </Trigger>
    </Style.Triggers>
</Style>
You can't hire a "UI designer" and expect them to contend with nonsense like that.
** UnhandledExceptionEventHandler :: OFFICIAL LC / CHATTER THREAD ** Quote
06-21-2017 , 10:55 PM
Quote:
Originally Posted by jmakin
No not yet
LINQ is a large part of what makes C# a good language.
** UnhandledExceptionEventHandler :: OFFICIAL LC / CHATTER THREAD ** Quote
06-21-2017 , 11:43 PM
Quote:
Originally Posted by ChrisV
What's the new hotness if not WPF then?
I dunno. Our big project right now is re-writing this particular app for the browser. There's UWP, but this says WPF isn't actually going anywhere. I think maybe I'm just remembering rumors from a couple years ago.

Quote:
Originally Posted by ChrisV
I'm not convinced that "UI designers who just write XAML" are a thing. You need to be a programmer to write XAML, because of the insistence on using XML not just for documents, like God intended, but for styling metadata, which is horribly verbose and unintuitive.
Good point. I recall the MS training guy trying to sell Blend to us on the basis of separating design. But that was probably 2012 or 2013. In practice we never did WPF development the way the MS people told us we were supposed to do. It's hard for me to tell you how much that's because MS was wrong vs. us being stupid.
** UnhandledExceptionEventHandler :: OFFICIAL LC / CHATTER THREAD ** Quote
06-22-2017 , 01:06 AM
Quote:
Originally Posted by just_grindin
Kerowo nailed it. It even directly references coding because I remember her discussing the lack of quality code for people to review over and over again and learn from to move past the mediocrity barrier (paraphrased terribly from the talk).



Sent from my SM-G900R4 using Tapatalk
Hmmm interesting what ted talk was it? I just ended my day which started at 8ish to 11pm applying/looking up jobs. I have an interview for junior rails dev and a launchcode interview set up. Just researching and finding suitable jobs is such a hassle, especially for my local region (Miami).

But I digress, let's get back to the chickens comparisons. I want to get better at python as I have the understanding and I'm betting it will become more established in the future. So for the time being I guess I'll stick to that.

Anyways if anyone wants to give me some pointers on my resume I would really appreciate it. I'm a little conflicted as to the deal with cover letters so for the most part I've been ignoring it especially with sites like LinkedIn "easy apply" button where you just submit a resume and that's it

Resume:
http://imgur.com/RRcjHJv
** UnhandledExceptionEventHandler :: OFFICIAL LC / CHATTER THREAD ** Quote
06-22-2017 , 03:45 AM
Third paragraph under marines. "scheduled"
** UnhandledExceptionEventHandler :: OFFICIAL LC / CHATTER THREAD ** Quote
06-22-2017 , 05:36 AM
To continue my WPF ranting: There's a control called StackPanel which is kind of like a div in HTML. To change the border on say a textbox, you set the BorderBrush and BorderThickness properties. To set properties like background color on a StackPanel, you set the Background property. But panels aren't allowed to have borders, if I want a border around my StackPanel I add a <Border> element around it in the document and style that. What the ****?
** UnhandledExceptionEventHandler :: OFFICIAL LC / CHATTER THREAD ** Quote
06-22-2017 , 09:02 AM
Quote:
Originally Posted by Larry Legend
Third paragraph under marines. "scheduled"
Ha! The power of the crowds. Thanks
** UnhandledExceptionEventHandler :: OFFICIAL LC / CHATTER THREAD ** Quote
06-22-2017 , 11:37 AM
Quote:
Originally Posted by ChrisV
LINQ is a large part of what makes C# a good language.
Yea, that looks pretty cool. I hate query languages but that makes it look kind of tolerable.
** UnhandledExceptionEventHandler :: OFFICIAL LC / CHATTER THREAD ** Quote
06-22-2017 , 12:02 PM
Quote:
Originally Posted by ChrisV
To continue my WPF ranting: There's a control called StackPanel which is kind of like a div in HTML. To change the border on say a textbox, you set the BorderBrush and BorderThickness properties. To set properties like background color on a StackPanel, you set the Background property. But panels aren't allowed to have borders, if I want a border around my StackPanel I add a <Border> element around it in the document and style that. What the ****?
It's been a few years since I used .Net, but I know I never used whatever you are describing. Not even sure why that exists at all. For the most part, it wasn't any different than [fav-lang] + template w/ external style sheets.
** UnhandledExceptionEventHandler :: OFFICIAL LC / CHATTER THREAD ** Quote
06-22-2017 , 12:27 PM
Hoy ****ing mother of god microsoft edge is terrible. I had it open because some website wouldnt work on firefox. I had 2 webpages open, nothing too crazy and no media at all, and it was consuming 1.2 gb's memory and was at like 20% cpu usage. Jfc.
** UnhandledExceptionEventHandler :: OFFICIAL LC / CHATTER THREAD ** Quote
06-22-2017 , 02:01 PM
Quote:
Originally Posted by daveT
It's been a few years since I used .Net, but I know I never used whatever you are describing. Not even sure why that exists at all. For the most part, it wasn't any different than [fav-lang] + template w/ external style sheets.
To continue with this, I don't think that XAML is supposed to be created by hand. One of my complaints about the VS in particular was the over-dependence on well... the visual aspects and generated code from the visual sections. It's especially dangerous if a non-coder makes a mistake that generates bad code.

The upside is that the designer, in theory, should be able to use an environment that is close enough to the tools he is familiar with (Photoshop), but this would be akin to having to open up the PS file in an editor to fix a bad border line.

As I said, I don't recall using XAML at all, but I do recall the UI designer creating and building C# code. I didn't like that at all.
** UnhandledExceptionEventHandler :: OFFICIAL LC / CHATTER THREAD ** Quote
06-22-2017 , 02:53 PM
Freaking angular changing their version-naming. Now we have to go through all kinds of bureaucratic hoops to get 4.x approved, when 4.0 is really 2.1.
** UnhandledExceptionEventHandler :: OFFICIAL LC / CHATTER THREAD ** Quote
06-22-2017 , 03:21 PM
Quote:
Originally Posted by Paramecium
Freaking angular changing their version-naming. Now we have to go through all kinds of bureaucratic hoops to get 4.x approved, when 4.0 is really 2.1.
fyp
** UnhandledExceptionEventHandler :: OFFICIAL LC / CHATTER THREAD ** Quote

      
m